Introduction of Calling Quick Screens as Functions

[chuck.reinke]

I believe the practice arose many years ago on ancient HP systems where
programmers often ran out of stack space. A GHOST screen, as a sub-process,
was a technique for gaining additional system resources. Eventually some
programming logic supported the technique as well as the idea of shared
subroutines.

Chuck

----- Original Message ----- 
From: "Darren Reely" <darren.reely@latticesemi.com>
To: <powerh-l@lists.sowder.com>
Sent: Monday, May 24, 2004 6:10 PM
Subject: Introduction of Calling Quick Screens as Functions


> We were wondering today when the concept was introduced allowing coders
> to call quick screens as hidden functions.  The code I'm maintaining
> seems to have been created as early as April 1992.
>
> While we're on the subject. What is the best way to set up the screen
> statement? Apparently the GHOST option is not _required_ when calling
> the screen.
>
> Thanks for the interest.
>
> Darren
>
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
powerh-l-request@lists.sowder.com
> Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.