In this case , I am more prone in an API to provide a Wrapper Class that provides a Serializable view , rather than make everything Serializable or not.
Leandro A. Pezzente. On viernes, 10 de febrero de 2012 at 4:41 PM, Gilles Sadowski wrote:Hi. This is an issue raised in relation to this JIRA ticket: https://issues.apache.org/jira/browse/MATH-742 My position is that there should not be a discussion each time someone wants a class to be "Serializable". Ideally, the rule should be clear enough that the developer of a new class knows whether it should be made "Serializable" or not. Either we decide to not get in the way, ever, by making everything "Serializable", or we think that some classes should be "Serializable" and others should not, for some reason. [And IMHO that reason should be more substantial than someone opening a ticket saying "Please make this class Serializable because I need it".] However, because the second alternative is likely to generate exhausting debates not worth the energy, I shall stop even trying to defend this point-of-view. ;) Best regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
