Talk:Memory allocation

From Rosetta Code

About langs like C, the task requires explanation about the fact that local variables are "allocated" on the stack (likely), so that a way of "allocating" 100 integers is simply int ints[100] ... even though this is not an explicit allocation? --ShinTakezou 16:51, 26 May 2009 (UTC)

Yes, please do explain the difference in lifetime and syntax of "auto" vs. malloc() allocations. --IanOsgood 16:53, 26 May 2009 (UTC)
POSIX should have also shmget and friends for shared memory (shared among processes, not threads)... but sincerely I've never used them :D --ShinTakezou 17:39, 26 May 2009 (UTC)

Task Applicability

I think this task does not apply to Tcl, and suspect it is not applicable to any other dynamic language either. They all leave memory management to their runtime; that's part of their charm. But I won't help them by marking tasks with {{Omit}} for them... —Dkf 19:11, 26 May 2009 (UTC)

I was hoping that even dynamic languages could show how to how to manage lifetimes of blocks of memory, for use in foreign function interfaces, for example. --IanOsgood 22:18, 26 May 2009 (UTC)