Strings doing what they are not supposed to...???
Ah, come on Wetboy...
You can't expect him to actually try to solve the problem himself when he
knows
he can come to good ole comp.lang.c and have it answered for him (of course
without any code that demonstrates the problem).
Just like my son (who's 19 by the way):
Son: Dad, what date is next Monday?
Dad: What is today's date?
Son: The 6th of April.
Dad: And how many days are in a week?
Son: 7.
Dad: And how much is 6 + 7?
Son: 13... Ohhhhhhh, THANKS DAD!!!
Dad: "Don't mention it (ever again)..."
He said gritting his teeth!
--
Best regards,
_ __ _ , _ _ _
' ) ) / _/_ ' ) / ' ) ) )
/--' ____/___/> __ / /--/ / / / __,_ __ o _ ______
/ \_(_) /_) (__/ (_<__ / ( o / ' (_(_) (_/ (_<_/_)_(_) / <_
Robert H. Morrison Tel: +49 721 9628 167
Software Development, Basis Team FAX: +49 721 9628 261
Quote:
> : I appreciate the advice that people have given me, but I allocated
space for
> : each string, checking for NULL pointers along the way, and it still
does the
> : same thing. I just can't figure out what's going wrong. Each time I
call this
> : initialize function, it works for the string that is passed into it,
but each
> : time it is called, it changes all of the strings that were called
previously.
> : I just can't see the logic. Does anyone know what is going on?!? I'm
really
> : stuck here.
> Suggestion -- maybe you've done this already -- compile your
> program in debug mode, and single step through to find out
> what is going on.
> -- Wetboy
