On Sat, 8 Jan 2005 19:04:41 +0100 Christian Biere <[EMAIL PROTECTED]> wrote:
> but this means that we must not use format strings with ngettext(). Although in my knowledge, it means human him/herself must confirm that whether its format is proper instead of compiler's auto checking, doesn't it? ...um, I don't know actually. > So the affected format strings have to be re-arranged that the > ngettext() result is a mere string argument - as discussed before > this might require context information to the translatable strings. I think it's the main problem, in a word, hack part you mentioned ahead. > GCC is clever enough so that it can check this at compile-time since > it's transparent macro in contrast to a function interface. > I assume this is no different from gettext() but GCC "trusts" the > latter to not mess with format strings. I don't always trust GCC, so I can understand what you want to say in different aspect though...well...I wish I had have MIPSpro compiler so that I can acquire certain view point. -- Daichi ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Gtk-gnutella-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gtk-gnutella-devel
