>You know better than to say that. calloc() initializes the
>allocted memory to zero while malloc() doesn't garantee anything
>about it's contents. That and the fact that calloc() is much
>slower than malloc() makes for a significant difference
>between the two. They are not interchangeable. Code that uses
>calloc() (eg- circle) often calloc()'s the memory for structures
>instead of malloc()'ing it and seperately initialing each field
>of the structure.
well, if everything is always set to something already (it should be)
why not use Malloc no matter what?
change of the macro is easy enough. what are possible faults in this
logic?
anyways, what was the last version(latest) of libc known to crash
with the line in medit.c (OasisOLC):
free(mob_index);
i know there are patches to fix this (such as George's I_CRASH addition)
but i'd like to know.
i have 5.4.33 and i can't change it to 5.4.38 b/c i don't have root
access.
i'd prolly d/l it myself, but its approximately 5-6MB of disk space
(not sure).
anyway, thanks for the help.
Akuma the Raging Coder
+------------------------------------------------------------+
| "The poets talk about love, but what I talk about is DOOM, |
| because in the end, DOOM is all that counts." - |
| Alex Machine/George Stark/Stephen King, The Dark Half |
| "Nothing is IMPOSSIBLE, Just IMPROBABLE" |
| "Easier Said Than Done, But Better Done Than Said..." |
+------------------------------------------------------------+
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST