> Now that the protocol is in Limbo anyways (and per Scott's idea) I would like > to go ahead and change it so that all fields that contain String values are > quoted, either by quotation marks around the string or a single ' at the > beginning of the field value. > > Being able to tell when reading a field whether it is a string or a value > would > make parsing the protocol a lot easier, since as it is now I don't know which > fields are until somebody calls the get() method of the FieldSet with a > numeric > default value. > > Any objections to this?
Yes--quoting is gross, and that part of the spec is the most solid and complete of any, thanks to lots of debate and feedback. All field values are strings, period. Unicode values 0x0020..0xFFFF. If some function wants to interpret one as a number, it should fetch the string and do the conversion itself. I have no objection if you want to add convenience methods to the FieldSet object for getInteger() or getHex() or whatever, but quoting is ugly, error-prone, and unnecessary. It adds comlexity without adding any functionality at all. -- Lee Daniel Crocker <lee at piclab.com> <http://www.piclab.com/lcrocker.html> "All inventions or works of authorship original to me, herein and past, are placed irrevocably in the public domain, and may be used or modified for any purpose, without permission, attribution, or notification."--LDC _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
