Path: utzoo!attcan!uunet!cbmvax!bryce
From: bryce@cbmvax.UUCP (Bryce Nesbitt)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Unsupported Programming Practices
Message-ID: <5642@cbmvax.UUCP>
Date: 7 Jan 89 23:37:44 GMT
References: <5605@cbmvax.UUCP> <10227@well.UUCP> <5632@cbmvax.UUCP> <10262@well.UUCP>
Reply-To: bryce@cbmvax.UUCP (Bryce Nesbitt)
Organization: Commodore Technology, West Chester, PA
Lines: 29

In article <10262@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>>>In article <5605> carolyn@cbmvax.UUCP (Carolyn Scheppner CATS) writes:
>>>>Do not execute code on your stack or put system structures on your stack.
>>>
>>>	I occasionally put RastPorts on my stack; does that count?
>
>	AARRGGHHH!  What a bloody nuisance.  Throwing temproary RastPorts
>       around on the stack has been a real nice win for me....
 
The recommendation about putting system structures on the stack is on the right
track--but may be safely ignored for now.  There needs to be a comprehensive
document on surviving in an MMU world, but that line is not it.  Panic
changes will hurt more than help.

Most of that "Unsupported Programming Practices" document was
about fatal things that cause problems now, or will soon.  The stack
comment is a bit out of place, sorry.


Executing code on the stack, however, IS FORBIDDEN.
Self-modifying code IS VERY, VERY DANGEROUS.
Depending on the speed of the CPU is JUST PLAIN DUMB.


|\_/|  . ACK!, NAK!, EOT!, SOH!
{O o} .     Bryce Nesbitt
 (")        BIX: bnesbitt
  U	    USENET: cbmvax!bryce@uunet.uu.NET -or- rutgers!cbmvax!bryce
Disclaimer: I'm not an official, and this is not an official opinion.