From: Justin D. <jde...@op...> - 2007-09-05 17:30:32
|
> > If a user needs to treat an InternationalString as a String, he can just invoke > toString(), which is defined in the javadoc. But I don't expect this need to > arise if InternationalString is not used as a programmatic name. I expect it to > be used in context like string concatenation (e.g. "Search result for " + title) > where String or InternationalString make no difference for the developper. Not necessarily, sometimes the devleoper does not have the freedom to call toString(). Think of a web framework that binds a form control to a property of a java bean. Will it know how to binding to InternationalString... probably not. Will be smart enough to work against CharSequence and not String... perhaps. And will the editor know how to create a new international string when the user changes the text in the form, almost certainly not. Anyways, i am not too worried about it since as you state martin its not a central point in the feature api. It is just that it seems wherever i look in geoapi and expect a simple construct, like a string, or a simple qualified name i see something complex. -Justin > > Martin > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Geotools-devel mailing list > Geo...@li... > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > !DSPAM:4007,46dee1a7219522458217002! > -- Justin Deoliveira The Open Planning Project http://topp.openplans.org |