> DN> Just out of interest, why cast the return from malloc()? If
 > DN> it is because it has no prototype, then you should do the
 > DN> /correct/ thing and include stdlib.h.

 > I have to cast it in Borland. In both TC2 and BC4 i'll get a
 > "cannot assign void* to char* error" otherwise

Oh. Then disable C++ mode - you're compiling in C++, not C.

 > it'll happen with both
 > ANSI, or Borland extensions used C or C++.

It won't happen in C mode. If it does, the compiler is broken. And Borland
wasn't *that* broken last time I looked at it.


 > DN> Excuse my bent towards better readability :-)

 > And what's wrong with my codes' readability ?
 > Dammit, i've "accidently" cut the evidence :)

:-)


 > I don't like strdup(), makes it a bit easy to forget to free the
 > string

How so? What's the difference between using it and malloc?

Library calls exist for a reason. strdup() is convenient and it avoids
unnecessarily repeating code. There is no reason not to use it.


 > DN> Note the 'const' in the parameters. It is a good idea to
 > DN> define the interface to a function as clearly as possible,
 > DN> which is why const exists. It also allows you to use the
 >
 > I always thought the main functionality of a const was to keep the
 > variables constant.

No, 'const' is an interface modifier. The /effect/ of using const pointers
is to prevent the compiler from modifying whatever it points to, but that's
the nature of the interface, and not really an expression of physical
"constness" of a variable.

For example, you could not use a "const char *" or "const
char []" type as a parameter to your function. You'd have to cast away
const, which is of course completely unnecessary.


 > i'd spend 90% of programming time there(being a DOS IDE).
 > BC4 does have it, so i'll have to keep it in mind, i normally do my
 > final compile with it.It tends to do a better optimize.Not on size. :)

With Borland compilers, its "optimisation" isn't crash hot
irrespective of the version. It's probably the most slothful of all the
major commercial PC compilers in that respect, which is of course why it
compiles comparatively quickly.

--- MaltEd/2 1.0.b6