Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-13 08:40:30 Link
Don't you hate it when you have a super long one-time conversion
program, add some new 1-time crap over time, and then all of the sudden
when ready to run you get this error message, AND CAN'T SEE WHERE THIS
MISSING/ERRANT STRUCTURE IS?
I'd be surprised if we haven't all been there at some point in our dev
lives.
It pays to take the time and do good modular design instead of this
way-too-long PRG run on crap. hahaha
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/5b3aaba876ba6d49dc5b61940945c331@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
I wrote something ages ago to deal with that type of thing. Basically
renders to HTML and puts the matched branching statements into div blocks
which were collapsible. Made it easy to find the issue.
Yes been there !!
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
mbsoftwaresolutions@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:41 PM
To: profoxtech@leafe.com
Subject: "An IF | ELSE | ENDIF statement is missing"
Don't you hate it when you have a super long one-time conversion program,
add some new 1-time crap over time, and then all of the sudden when ready to
run you get this error message, AND CAN'T SEE WHERE THIS MISSING/ERRANT
STRUCTURE IS?
I'd be surprised if we haven't all been there at some point in our dev
lives.
It pays to take the time and do good modular design instead of this
way-too-long PRG run on crap. hahaha
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/001501d2fbdf$0b673e40$2235bac0$@ozemail.com.au
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: mbsoftwaresolutions@mbsoftwaresolutions.com
Posted: 2017-07-13 08:56:56 Link
On 2017-07-13 09:50, Darren wrote:
> I wrote something ages ago to deal with that type of thing. Basically
> renders to HTML and puts the matched branching statements into div
> blocks
> which were collapsible. Made it easy to find the issue.
>
> Yes been there !!
You should upload that to the ProFox downloads page for the community's
benefit! ;-)
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/244f21bf0be310b66b58f93917ed826e@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
And another tool I have which helps is to add comments to the end of the
terminating commands - e.g. ENDIF, ENDFOR, ENDDO, EXIT etc. which help to
identify the branch / loop.
Viz.
Without terminating comments...
DO WHILE .T.
*- Operate between 1am and 3pm local sydney time
IF NOT BETWEEN(HOUR(DATETIME()), 1, 15) && 01:00:00 to 14:59:59
=messagebox("This function is designed to run between 1am and 3pm
local time (Sydney)" + CHR(13) + CHR(13) + ;
"The program will now terminate", 48, "Outside of times of
operation", 10000)
EXIT
ENDIF
SELECT w_bnTrack
SCAN FOR rssAvailable
*- Check if this track has runs today.
SELECT w_usdRace
LOCATE FOR track_code = w_bnTrack.livetkcode
IF NOT FOUND()
SELECT w_bnTrack
LOOP
ENDIF
... With terminating comments...
DO WHILE .T.
*- Operate between 1am and 3pm local sydney time
IF NOT BETWEEN(HOUR(DATETIME()), 1, 15) && 01:00:00 to 14:59:59
=messagebox("This function is designed to run between 1am and 3pm
local time (Sydney)" + CHR(13) + CHR(13) + ;
"The program will now terminate", 48, "Outside of times of
operation", 10000)
EXIT && DO WHILE .T.
ENDIF && NOT BETWEEN(HOUR(DATETIME()), 1, 15) && 01:00:00 to 14:59:59
SELECT w_bnTrack
SCAN FOR rssAvailable
*- Check if this track has runs today.
SELECT w_usdRace
LOCATE FOR track_code = w_bnTrack.livetkcode
IF NOT FOUND()
SELECT w_bnTrack
LOOP
ENDIF && NOT FOUND()
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
mbsoftwaresolutions@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:41 PM
To: profoxtech@leafe.com
Subject: "An IF | ELSE | ENDIF statement is missing"
Don't you hate it when you have a super long one-time conversion program,
add some new 1-time crap over time, and then all of the sudden when ready to
run you get this error message, AND CAN'T SEE WHERE THIS MISSING/ERRANT
STRUCTURE IS?
I'd be surprised if we haven't all been there at some point in our dev
lives.
It pays to take the time and do good modular design instead of this
way-too-long PRG run on crap. hahaha
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/001801d2fbe0$3ecd3e50$bc67baf0$@ozemail.com.au
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
I could do that - not right now though - just on midnight here and about to
hit the hay.
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
mbsoftwaresolutions@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:57 PM
To: profoxtech@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"
On 2017-07-13 09:50, Darren wrote:
> I wrote something ages ago to deal with that type of thing. Basically
> renders to HTML and puts the matched branching statements into div
> blocks which were collapsible. Made it easy to find the issue.
>
> Yes been there !!
You should upload that to the ProFox downloads page for the community's
benefit! ;-)
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/001c01d2fbe0$bd56bcb0$38043610$@ozemail.com.au
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Paul H. Tarver
Posted: 2017-07-13 10:00:20 Link
Sometimes, the Beautify command can help with this. The indenting helps me
find where I'm off track or at least isolate the general area where the
problem starts.
Paul H. Tarver
Tarver Program Consultants, Inc.
Email: paul@tpcqpc.com
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
mbsoftwaresolutions@mbsoftwaresolutions.com
Sent: Thursday, July 13, 2017 8:41 AM
To: profoxtech@leafe.com
Subject: "An IF | ELSE | ENDIF statement is missing"
Don't you hate it when you have a super long one-time conversion program,
add some new 1-time crap over time, and then all of the sudden when ready to
run you get this error message, AND CAN'T SEE WHERE THIS MISSING/ERRANT
STRUCTURE IS?
I'd be surprised if we haven't all been there at some point in our dev
lives.
It pays to take the time and do good modular design instead of this
way-too-long PRG run on crap. hahaha
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/020f01d2fbe8$bf83dc40$3e8b94c0$@tpcqpc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Laurie Alvey
Posted: 2017-07-13 12:32:15 Link
Apart from all of the above, my pet hate is mistakenly using ERRANT instead
of ERRING. ERRING means in error and ERRANT means on a mission (as in "A
Knight Errant"). I'm sure as children we all had to run ERRANDS (same root).
Laurie
On 13 July 2017 at 16:00, Paul H. Tarver <paul@tpcqpc.com> wrote:
> Sometimes, the Beautify command can help with this. The indenting helps me
> find where I'm off track or at least isolate the general area where the
> problem starts.
>
> Paul H. Tarver
> Tarver Program Consultants, Inc.
> Email: paul@tpcqpc.com
>
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
> mbsoftwaresolutions@mbsoftwaresolutions.com
> Sent: Thursday, July 13, 2017 8:41 AM
> To: profoxtech@leafe.com
> Subject: "An IF | ELSE | ENDIF statement is missing"
>
> Don't you hate it when you have a super long one-time conversion program,
> add some new 1-time crap over time, and then all of the sudden when ready
> to
> run you get this error message, AND CAN'T SEE WHERE THIS MISSING/ERRANT
> STRUCTURE IS?
>
> I'd be surprised if we haven't all been there at some point in our dev
> lives.
>
> It pays to take the time and do good modular design instead of this
> way-too-long PRG run on crap. hahaha
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAMvTR9fQU4fwWso3yO965ntyTLKTgNiHg0JraJT=95DSa6X=Aw@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Michael Glassman
Posted: 2017-07-13 12:36:41 Link
Errant is correct. It has two meanings as an adjective:
1. erring or straying from the proper course or standards.
"he could never forgive his daughter's errant ways"
synonyms: offending, guilty, culpable, misbehaving, delinquent,
lawbreaking
2. archaic/literary: traveling in search of adventure.
"that same lady errant," "a knight errant"
synonyms: traveling, wandering, itinerant, roaming, roving, voyaging
Mike
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Laurie
Alvey
Sent: Thursday, July 13, 2017 11:32 AM
To: profoxtech@leafe.com
Subject: Re: "An IF | ELSE | ENDIF statement is missing"
Apart from all of the above, my pet hate is mistakenly using ERRANT instead
of ERRING. ERRING means in error and ERRANT means on a mission (as in "A
Knight Errant"). I'm sure as children we all had to run ERRANDS (same root).
Laurie
On 13 July 2017 at 16:00, Paul H. Tarver <paul@tpcqpc.com> wrote:
> Sometimes, the Beautify command can help with this. The indenting
> helps me find where I'm off track or at least isolate the general area
> where the problem starts.
>
> Paul H. Tarver
> Tarver Program Consultants, Inc.
> Email: paul@tpcqpc.com
>
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of
> mbsoftwaresolutions@mbsoftwaresolutions.com
> Sent: Thursday, July 13, 2017 8:41 AM
> To: profoxtech@leafe.com
> Subject: "An IF | ELSE | ENDIF statement is missing"
>
> Don't you hate it when you have a super long one-time conversion
> program, add some new 1-time crap over time, and then all of the
> sudden when ready to run you get this error message, AND CAN'T SEE
> WHERE THIS MISSING/ERRANT STRUCTURE IS?
>
> I'd be surprised if we haven't all been there at some point in our dev
> lives.
>
> It pays to take the time and do good modular design instead of this
> way-too-long PRG run on crap. hahaha
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/016801d2fbfe$973280a0$c59781e0$@PioneerDrama.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Malcolm Greene
Posted: 2017-07-13 12:51:50 Link
Not to hijack this thread, but Python's indentation-as-syntax eliminates
problems like this. I know this doesn't solve the problem at hand, just
pointing out how another language handles this situation.
Malcolm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1499968310.1902152.1040019064.725118F8@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Author: Laurie Alvey
Posted: 2017-07-13 13:41:47 Link
Mike,
Thanks for for your clarification. Errant (in the sense of erring) comes
from the Latin "errare", to err. Errant (in the sense of on a mission)
comes from Old French (travelling). English has plenty of words which are
spelt the same but have different meanings, e.g. cleave.
Laurie
On 13 July 2017 at 18:51, Malcolm Greene <profox@bdurham.com> wrote:
> Not to hijack this thread, but Python's indentation-as-syntax eliminates
> problems like this. I know this doesn't solve the problem at hand, just
> pointing out how another language handles this situation.
>
> Malcolm
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAMvTR9c7B2vDGVgiCL1j+0oXrQYn5+5gfVwNO1c7UvHPMpueTA@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.