Introduction of Calling Quick Screens as Functions

[Deskin, Bob]

The capability of a ghost screen or invisible subroutine was always present in QUICK. For simple systems, it was useful for common routines. As applications became more complex and bigger, stack space on the HP3000 MPE V systems became an issue as Chuck mentions. If you could break out the complex processing into one or more ghost screens, you could actually fit your application into the fixed stack space.

As for the best way to do things, it depends what you need to do. Obviously there's no need for a layout section but that does not preclude you from using the ENTRY procedure. Most ghost screens use either the INITIALIZE or the ENTRY procedures. File work is usually done with a DESIGNER file. Every now and then you can get caught by QUICK's ingrained assumptions about what it's doing.

Note that while QUICK has this capability, it's not specifically designed for it. But then QUICK was originally released as a file maintenance utility.

Bob Deskin              
Product Manager, Application Development Tools
Cognos Inc. 3755 Riverside Drive, Ottawa ON K1G 4K9 CANADA
bob.deskin@cognos.com (613) 738-1338 ext 7268

-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of chuck.reinke
Sent: May 24, 2004 10:27 PM
To: Darren Reely; powerh-l@lists.sowder.com
Subject: Re: Introduction of Calling Quick Screens as Functions


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.


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
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. 
  
       This message may contain privileged and/or confidential information.  If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so.  Thank you.