|
Not sure whether I was misinterpreted. I was intending to extend your idea of forgoing all subroutines "for two to three months just to get into practice." Sometimes I need to be "coerced" like that. <g> By the BTW: Enforcing this "no subroutines" idea would almost have to take into account existing apps that have myriad SR's. The pre-compiler option could look at the source statement mod date and kick out those with a higher date than... Like I have nothing better to do. <g> GA --- rob@xxxxxxxxx wrote: > I think that what you are saying is that if it's so simplistic that you > don't want to bother with PI's/PR's then you wouldn't want to bother with > BEGSR's/EXSR's. Interesting thought. > > By the way, I compiled a very simple program with a subroutine in it just > to see if it generated any messages like RNF#### - list of subroutines. > Nothing. Too bad, if there was I bet you could have CHGMSGD and kicked up > the severity to a higher number. And that would have stopped the > compiler. I bet that's a technique not published in "How to Win Friends > and Influence People". :-) > > Rob Berendt __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
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.