CVS update: samba/source/lib

[Elrond]

On Tue, Aug 15, 2000 at 03:54:55AM +1000, Tim Potter wrote:
> Elrond writes:
> 
> > I consider const char *get_nt_error_msg(uint32 nt_code) a
> > proper and secure interface. You get a nice pointer into
> > memory, that you're not allowed to write to. You have to
> > decide on yourself, what you do with it.
> 
> Except for the fact that const produces sooo many compiler
> warnings on most systems.  )-:

Well...

a) I don't care. ;) Normal "users" are used to hundreds of
   warnings from normal compiles... When I compile xyz, I
   also ignore all the warnings (unless I want to debug it,
   of course)
b) Normaly configure should check for proper handling of
   const by the compiler and if it doesn't handle const
   properly it should add some "#define const /* empty */"
   to config.h
c) gcc handles it correctly and so it becomes a good tool
   for tracking/enforcing proper code.


    Elrond