-= Pete Replied to David Nugent about: Find a word =-

G'day David

 > FA> char *txt;char *pat;char *ptr;
 > FA> txt = (char*) malloc(strlen(buf)+1);
 > FA> pat = (char*) malloc(strlen(wrd)+1);

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

I've always cast the return from malloc() to whatever type the
receiving pointer was as i always assumed it had to be done? BTW just
tried it without the cast and all worked without any warnings/errors
being generated with the compiler (QC) set to highest warning level,
looks like i'll save myself some typing in the future.

 DN> If the compiler implements it and stack space isn't going to be
 DN> a problem, you could use alloca() for the temporary strings.
 DN> alloca() is usually significantly faster than the standard heap
 DN> allocation functions, and freeing is automatic.

I've never used alloca() in fact i never knew it existed till you just
mentioned it, just looked it up and it comes with a warning, see
below.

========== from QC online help ============
Use of the alloca function is not recommended. The function is
supported only for source compatibility with earlier releases.
Routines using alloca should be compiled with optimization turned off
(i.e., with the /Od option).

When you compile with optimization on (either by default or by using
one of the /O options), the stack pointer may not be restored
properly in functions that have no local variables and also reference
the alloca function. To ensure that the stack pointer is properly
restored, make sure that any function referencing alloca declares at
least one local variable.
============================================

looks like without local varables the BP/SP reg's are not saved and
restored when optimizations are turned on.

   -=Pete=-


--- OMX/Blue Wave v2.12