Reply to thread

Message: [QUOTE="Keith Thompson, post: 2891664"] When posting a followup, you should usually quote the relevant parts of the parent article. See most of the articles here for examples. See also <[URL]http://cfaj.freeshell.org/google/[/URL]>. In this particular case, your followup is probably clear enough without quoted context, but keep it in mind for future postings. You need to be aware that Google Groups is *not* Usenet. Usenet is a distributed discussion forum that has existed for several decades. Google Groups is, among other things, an archive of Usenet and a (sometimes rather inconvenient) interface to it. comp.lang.c is a Usenet newsgroup; Google Groups does not own it. In general, the trick is to find a forum where your questions are topical. There may be a Usenet newsgroup that fits your needs. If not, Google Groups may have some non-Usenet group. [...] I don't know what you mean by "terminal". Are you working with some kind of embedded system? If you need dynamically allocated storage that's can be deallocated before the program terminates, and that doesn't vanish at the end of the scope in which it's created, then malloc() and friends are the only tool the C language offers. If your implementations's malloc() is somehow broken, you may be able to roll your own. For example, you might declare a sufficiently large static array, and provide your own functions to allocate chunks from it. I think K&R2 has a sample memory allocator; it might be instructive. If you don't need the full generality of malloc, realloc, and free, that might make rolling your own a bit simpler. For example, if all your allocations are the same size, you don't need to worry about fragmentation. If your allocated chunks of memory are always going to be deallocated in the reverse of the order in which they were allocated, you can use a stack-like scheme. And so on. [snip] [/QUOTE]

Verification