Yeah, that's the crap I had suspected.  (Wrt my previous reply, included
below in case it gets the axe.)  I noticed similar symptom in debugging
code.

And if I hafta relearn how a cottin-pickin AND works.. well...  dag.  (I'm
exhausted, and it shows I s'pose.)

| -----Original Message-----
| [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Gerald Magnuson
| Sent: Thursday, March 25, 2004 12:08 PM

| Hans,
| Are you saying it makes a difference
| if we have the "and" on the top line,
| or on the next line?
| Could you explain why that is?
|

| -----Original Message-----
| From: jt [mailto:jt@xxxxxx]
| Sent: Thursday, March 25, 2004 12:35 PM

| I believe it needs to be:
|
| dow       pos < 52 and
|           (InputMAD(pos) <> ';')
| eval      pos = pos + 1
| enddo
|
| Because if ';' not found, it will eventually try to evaluate
| InputMAD(53).  Now this assumes that the dow is evaluated in the
| order of checking the first test and if it passes then the second
| test.  Which is how it used-ta do, but I'm not absolutely certain
| with this newfangled stuff.  (Jes LOVE to hafta guess this kind-a
| thing...)-;




As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.