Hi, > Well in the Adobe days we'd put the code change behind a version flag. I > never liked those flags if they controlled more than one code path because > you had to take all new code paths or none. I also dislike that them but it is a solution, I think there only been one or two done since donation.
> Lately I've put static flags in the class in question so you can change > the code paths that way. > > So, if you create a getDataSafely() function with the try/catch in it and > hide that behind a flag then folks can revert back to old behavior if > necessary. Seems the best way - generally knowing about RTEs in your code is good thing. Thanks, Justin
