[Coco] NitrOS-9 boot module common code

[Roger Taylor]

At 03:58 AM 5/12/2010, you wrote:
>The C language does this, often keeping small stuff on the stack.  it also
>does its own housekeeping so you don't have to, at least as long as the
>original c.prep has been replaced with c.prep19 so can write programs bigger
>than about 10k of src.

Right, CCASM even builds procedure code that uses the stack, but 
during the boot process of OS-9 I'm not aware of where the stack is.



>An F$RegDump at that point, just once I believe, would tell you how much room
>there is on the stack.  The point is that when you allocate memory by that
>method, there is only the housekeeping that you do to clean up the mess, and
>since the system has no knowledge of the shortcut allocation, it may, for
>some other program, allocate memory from what you thought was your own
>private pool, and that can lead to 'interesting' results.  I wouldn't think
>that it would be a problem as long as the system ram stays above a kilobyte
>or more free.  F$RegDump can tell you that at that particular point.

-- 
~ Roger Taylor
http://liveshots.blogs.foxnews.com/2010/05/12/on-the-job-hunt-ups/?test=latestnews