Dennis Clarke wrote:
----------------------------------------------------
Regarding the i18n code, do we have any sort of detailed specs on it such that
a motivated programmer could sit down with a stack of POSIX books and just
begin to hammer it out from first principals? I mean, without doing something
obscene like reverse engineering or simple disassembly.
Dennis
ps: sorry about the lack of message indenting but Sun Convergence isn't doing
that for me this morning. Thankfully it does not break maillist threads.
Dennis
The task is very clear..
#1 Take the closed bin.. extract.. run objdump on it to determine the
symbol(s) (which will probably match the name of the file) This is an
interface to a POSIX compliant function as you realize..
#2 Take Citrus from NetBSD and see how they implemented it. (In many
cases it will be trivial)
#3 QA/fix bugs.. (Simply build a static archive like they do and see if
it works as a suitable drop-in replacement)
Steps 1-2 shouldn't take long tbh and the POSIX books are probably not
even required if the NetBSD compatibility can be believed.
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
