Here's the situation (as I understand it): Parrot needs to stop emitting strings exclusively in English. Parrot needs a standard file format for a string replacement db. Parrot should only put strings to stderr (except when told to). Parrot should be able to emit "error IDs" instead of strings. Parrot presently has about 200 strings that are targets.
Here's what I propose: A standard library that allows loading of a strings db at run-time based upon a defined order of variable testing. This might mean that the library would getenv a variable, then check for a command-line option, then check for the default Parrot value. A string database that has number/value pairs, where the number corresponds to the error number defined by Parrot, and the value is the string to emit for that number. A configure directive that tells the library to emit only error numbers only (no strings). This would then allow any language built on top of Parrot to intercept these codes for it's own purpose without having to parse a string. A tool for managing the strings db. This would need to include adherence to some sort of yet-undefined standard of assigning error codes. Perhaps using SOAP? a socket connection to CPAN? Any ideas are welcome. Bibliography: http://dev.perl.org/rfc/85.pod - RFC 85 http://dev.perl.org/rfc/296.pod - RFC 296 http://dev.perl.org/rfc/313.pod - RFC 313 Please comment. Grant M. [EMAIL PROTECTED]
