On Fri, Apr 05, 2013 at 09:15:11PM -0400, Conor Walsh wrote: > Detailed? What's kept beyond "a called b (arguments...)" ? That's not a > lot of bytes, unless it's complete deep copies of structures.
The activation record is itself not large, but many calls do add up. The larger problem is that any memory allocated inside a function is only freed when the function call returns. So a deeply nested stack uses more memory beyond the activation records. Depending on the function, it could be substantially more. -Gyepi _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
