On Mon, Jun 28, 2010 at 4:15 PM, Stephan Assmus <superstippi@xxxxxx> wrote: > > Sometimes the BeBook got it wrong. The R5 header is the definite answer. :-) > Not having access to R5, what is the definite answer in this case? And If it is indeed not a const char* in R5, will making it a const char* break binary compatibility? -- Wim van der Meer \/\///\/\