× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




> > You can have subprocedures and "NOMAIN" without any conflict.   NOMAIN
> > means that you won't have a main procedure.  You can have both a main
> > procedure and subprocedures both in the same module without any problems.
>
> Do you mean sub-procedures and the <i>lack</i> of "nomain"? Can you have
> a MAIN procedure with "nomain"?  I don't think so... the cycle must
> exist for an *ENTRY point, mustn't it?

NOMAIN specifically means that there is no main procedure.  That's why
it's called "no main."  :)

Did I phrase it incorrectly the first time?

Perhaps 90% of the subprocedures that I write go into the same source
member as my main procedure.  I use them in a similar fashion to the way
you'd use a subroutine.

The other 10% of the time, I'm writing something that can be used from
many different places -- those routines get put into a "H NOMAIN" source
member, which gets compiled/bound into a service program with other
similar procedures.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.