×
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.
I used to suggest to my colleagues that they systematically put the name of a sub procedure in the end specification instead of :
D E
Our prototypes our declared in the source of the module. When searching for the name of a sub procedure in the source, you get a hit in a comment line before the prototype, the PR declaration, the comment before the sub procedure, the B declaration, the PI declaration, the call to the subprocedure and maybe other comments, but : never in the end of the subprocedure even though the subprocedure might be pages and pages of code.
Well, this still hasn't caught on. So I've decided, if you can't beat'em, join'em and I no longer put the name of the subprocedure in the end spec. It makes for quicker compiling, as I always copy another sub procedure and forget to change the name at the end spec.
My reasoning that the end spec name isn't necessary : if I can't see the start spec on the same page (ok 2 pages for greenscreeners), then my sub procedure is probably too dang long!!!!
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
