I would like to drop / modify serialization for the following: * Drop from all UnivariateRealSolvers. The API is not stable enough to be tied to the physical implementation (there are lots of protected fields, including a UnivariateRealFunction, which does not have to be serializable and I would be -1 to forcing this). If kept, custom serialization needs to be added and it is not clear to me how this should work.
* Drop from ContinuedFraction (no reason to serialize, burdens subclasses). * Drop from special functions, add argumentless constructors so subclasses can implement if desired (I see no reason to serialize these). * Drop from ValueServer (needs custom serialization, not worth the effort). * Either drop or customize serialization for all classes in the univariate package (other than StatisticalSummaryValues), especially those in the moment subpackage. Default serialization ties us to the current physical implementation, which may well change as we optimize implementations. For example, SummaryStatisticsImpl currently holds a (redundant) private field n. Removing this field after release would break backward serialization compatability. I will probably eliminate this field before release, but this is the kind of thing that makes me want to be conservative about serialization. My vote would be to release 1.0 without serialization support for these classes. Sorry to sound like a broken record on this; but I am just not comfortable releasing the above classes with default serialization. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
