G'Day David,
 
-=> Quoting David Nugent to Frank Adam <=-

 DN> It won't happen in C mode. If it does, the compiler is broken. And
 DN> Borland  wasn't *that* broken last time I looked at it.
Ok, it's fixed, the file extension must also be .C instead of .cpp. 
 
 > I don't like strdup(), makes it a bit easy to forget to free the
 > string
 DN> How so? What's the difference between using it and malloc?
 DN> Library calls exist for a reason. strdup() is convenient 
 DN> and it avoids unnecessarily repeating code. There is no 
 DN> reason not to use it.
It's one of those things, there are times when certain functions are 
perfect for a job no doubt, but because i don't use them often they 
would be the last thing that pop in my mind, and normally by then the 
job would be solved another way.


 DN> No, 'const' is an interface modifier. The /effect/ of using 
 DN> const pointers is to prevent the compiler from modifying 
 DN> whatever it points to, but that's the nature of the 
 DN> interface, and not really an expression of physical 
 DN> "constness" of a variable.
I guess not, as far as i know the variable can still be changed via
 
 
 DN> With Borland compilers, its "optimisation" isn't crash hot 
 DN> irrespective of the version. It's probably the most 
 DN> slothful of all the major commercial PC compilers in that 
Yep, i haven't heard too much good about Borland's compiler, all good 
words were directed to their debugger,IDE,and tprof.
Perhaps i'll surprise myself with Watcom 10-ish for xmas,or after the 
end of the financial year depending on how much Costello will grab.


  L8r Frank (fadam{at}ozemail.com.au).
  
___ Blue Wave/DOS v2.21

--- Maximus 3.01