RE: "An IF | ELSE | ENDIF statement is missing"

[Darren]

Yep I know - but with the && the syntax colouring in the editor makes it a
whole lot easier to read. 

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of AndyHC
Sent: Sunday, 16 July 2017 10:27 PM
To: profoxt...@leafe.com
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

you don't need the comment markers - this works just fine:
x=1
IF x=1
WAIT WINDOW 'true'
ENDIF x=1


Darren wrote:
...
With terminating comments...
> ...
>  IF NOT BETWEEN(HOUR(DATETIME()), 1, 15)  && 01:00:00 to 14:59:59
>
>=messagebox(
>
>  ENDIF && NOT BETWEEN(HOUR(DATETIME()), 1, 15)  && 01:00:00 to
14:59:59
>  
>

[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/011001d2fe30$340dca50$9c295ef0$@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[AndyHC]

you don't need the comment markers - this works just fine:
x=1
IF x=1
WAIT WINDOW 'true'
ENDIF x=1


Darren wrote:
...
With terminating comments...

...
 IF NOT BETWEEN(HOUR(DATETIME()), 1, 15)  && 01:00:00 to 14:59:59
   
   =messagebox(
   
 ENDIF && NOT BETWEEN(HOUR(DATETIME()), 1, 15)  && 01:00:00 to 14:59:59
 



___
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/416a9af4-ac18-4f08-6af6-f6b14ab3f...@hawthorncottage.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.

Re: "An IF | ELSE | ENDIF statement is missing"

[mbsoftwaresolutions]

On 2017-07-14 08:59, Ted Roche wrote:

On Thu, Jul 13, 2017 at 9:40 AM,
 wrote:
Don't you hate it when you have a super long one-time conversion 
program,


This is another good justification for printouts. Every few months, we
print out long listings, break out the multi-colored highlighters, and
mark up the code until we find the dangling reference.



Turned out I had an unmatched #IF/#ENDIF after I had commented out some 
older code.  Problem solved (for now).


___
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/5da2972b87096ed88fd62485c7b46...@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Koen Piller]

Does Beautify not do What you want?
Koen

Op vr 14 jul. 2017 om 17:17 schreef Richard Kaye <rk...@invaluable.com>

> Thor comes with a bunch of utility PRGs that might help with this. And you
> can create your own variations of pretty much all the Thor utilities if it
> doesn't work precisely as you want.
>
> --
>
> rk
>
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave
> Crozier
> Sent: Friday, July 14, 2017 8:37 AM
> To: profoxt...@leafe.com
> Subject: RE: "An IF | ELSE | ENDIF statement is missing"
>
> I feel your pain!
>
> I TRY and keep the rule that no tabbed programming structure (if... endif,
> do case.. endcase etc.) should span more than a page. but must admit I
> fail regularly!!!
>
> Dave
>
>
> -Original Message-
> From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of
> mbsoftwaresoluti...@mbsoftwaresolutions.com
> Sent: 14 July 2017 13:03
> To: ProFox Email List <profox@leafe.com>
> Subject: Re: "An IF | ELSE | ENDIF statement is missing"
>
> On 2017-07-14 07:39, Laurie Alvey wrote:
> > I was wondering if Intellisense would help (IFELSE).
>
>
> No.  Intellisense doesn't prevent you from writing sloppy way-too-long
> code.  lol
>
[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/cacuu1svv+aw7ehz8kqn2hr3pnm_ou8per6tzxi1ampvtuho...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Richard Kaye]

Thor comes with a bunch of utility PRGs that might help with this. And you can 
create your own variations of pretty much all the Thor utilities if it doesn't 
work precisely as you want.

--

rk

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave Crozier
Sent: Friday, July 14, 2017 8:37 AM
To: profoxt...@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"

I feel your pain!

I TRY and keep the rule that no tabbed programming structure (if... endif, do 
case.. endcase etc.) should span more than a page. but must admit I fail 
regularly!!!

Dave


-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of 
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: 14 July 2017 13:03
To: ProFox Email List <profox@leafe.com>
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

On 2017-07-14 07:39, Laurie Alvey wrote:
> I was wondering if Intellisense would help (IFELSE).


No.  Intellisense doesn't prevent you from writing sloppy way-too-long code.  
lol

[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/mwhpr10mb1774dfa5c6a539b4f93d6f40d2...@mwhpr10mb1774.namprd10.prod.outlook.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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Ted Roche]

On Thu, Jul 13, 2017 at 9:40 AM,
 wrote:
> Don't you hate it when you have a super long one-time conversion program,

This is another good justification for printouts. Every few months, we
print out long listings, break out the multi-colored highlighters, and
mark up the code until we find the dangling reference.

-- 
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com

___
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/CACW6n4tVJe=fro1hdfs_dmcfldbbc5newdixhffwqbk_zjf...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Dave Crozier]

I feel your pain!

I TRY and keep the rule that no tabbed programming structure (if... endif, do 
case.. endcase etc.) should span more than a page. but must admit I fail 
regularly!!!

Dave


-Original Message-
From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of 
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: 14 July 2017 13:03
To: ProFox Email List <profox@leafe.com>
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

On 2017-07-14 07:39, Laurie Alvey wrote:
> I was wondering if Intellisense would help (IFELSE).


No.  Intellisense doesn't prevent you from writing sloppy way-too-long code.  
lol

[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/18725b8cd2d5d247873a2baf401d4ab2b46e4...@ex2010-a-fpl.fpl.LOCAL
** 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.

Re: "An IF | ELSE | ENDIF statement is missing"

[mbsoftwaresolutions]

On 2017-07-14 07:39, Laurie Alvey wrote:

I was wondering if Intellisense would help (IFELSE).



No.  Intellisense doesn't prevent you from writing sloppy way-too-long 
code.  lol


___
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/7181c37eb8c152f209cc6c4ca5189...@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Laurie Alvey]

I was wondering if Intellisense would help (IFELSE).

Laurie

On 14 July 2017 at 12:32, 
wrote:

> On 2017-07-13 16:34, Ted Roche wrote:
>
>> On Thu, Jul 13, 2017 at 9:40 AM,
>>  wrote:
>>
>>>
>>> It pays to take the time and do good modular design instead of this
>>> way-too-long PRG run on crap.  hahaha
>>>
>>>
>> So, wait, you're saying that if you create functions/modules/methods
>> that are short, do only one thing, having clearly defined input and
>> output ranges and values, can be tested in isolation, have clear entry
>> and exit points, have a consistent error handling, are orchestrated
>> together,...  in other words, good coding is easier to debug?
>>
>> Hunh. I learn something new on this forum every day.
>>
>
>
> We've all been there:  "Oh this is a quick one-time only kind of thing.
> I'll just write some quick code."  ...and then it morphs into something
> larger and hairier before long.
>
[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/CAMvTR9dh7=oMihXX5Ptzbf8F9y8_toVmp=7uxkoxymlz3ze...@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[mbsoftwaresolutions]

On 2017-07-13 16:34, Ted Roche wrote:

On Thu, Jul 13, 2017 at 9:40 AM,
 wrote:


It pays to take the time and do good modular design instead of this
way-too-long PRG run on crap.  hahaha



So, wait, you're saying that if you create functions/modules/methods
that are short, do only one thing, having clearly defined input and
output ranges and values, can be tested in isolation, have clear entry
and exit points, have a consistent error handling, are orchestrated
together,...  in other words, good coding is easier to debug?

Hunh. I learn something new on this forum every day.



We've all been there:  "Oh this is a quick one-time only kind of thing.  
I'll just write some quick code."  ...and then it morphs into something 
larger and hairier before long.


___
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/d7a630671d5f6207d764dd83b1234...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Darren]

No not at all.  Only one place - the function adds the comments so one can
more easily work out what issues with branching and matching keywords. Then
another function magically removes them.  Regular expressions being your
friend in this case.


-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene
Wirchenko
Sent: Friday, 14 July 2017 2:42 PM
To: profoxt...@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"

At 06:59 2017-07-13, "Darren" <fox...@ozemail.com.au> wrote:
>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.

  I dislike the clutter intensely, and if the condition changes, there
are then two places to change.

[snip]

>... 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", 1)
>
>   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()

  If you really need this to keep your nesting straight, you have too
much nesting.

[snip]

Sincerely,

Gene Wirchenko


[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/001601d2fc5b$d53c5490$7fb4fdb0$@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Gene Wirchenko]

At 06:59 2017-07-13, "Darren"  wrote:

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.


 I dislike the clutter intensely, and if the condition changes, 
there are then two places to change.


[snip]


... 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", 1)

  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()


 If you really need this to keep your nesting straight, you have 
too much nesting.


[snip]

Sincerely,

Gene Wirchenko


___
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/99cb763296cd638f2f48d19aad910c81@mtlp86
** 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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Paul H. Tarver]

Sorry but I couldn't resist. :)

I thought everyone knew FOX = FUN!

Paul H. Tarver
Tarver Program Consultants, Inc.
Email: p...@tpcqpc.com 



-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Kurt
Wendt
Sent: Thursday, July 13, 2017 3:27 PM
To: profoxt...@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"

Hey  Paul - I think your reply is more in the way of Derailment instead of
HiJacking!
:-)

I must admit - sometimes when I want a little break from work - I come hang
out here in the land of ProFox - just for the entertainment value it affords
me!

Regards,
Kurt Wendt
Senior Systems Analyst 


Tel. +1-212-747-9100
www.GlobeTax.com

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul H.
Tarver
Sent: Thursday, July 13, 2017 4:14 PM
To: profoxt...@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"

Not to hijack this thread, but were you two talking about Monty and the
errant for the Holy Grail? :)

Paul H. Tarver
Tarver Program Consultants, Inc.
Email: p...@tpcqpc.com


-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul
Hill
Sent: Thursday, July 13, 2017 2:11 PM
To: profoxt...@leafe.com
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

On 13 July 2017 at 18:51, Malcolm Greene <pro...@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.

It makes it worse!  It's the number one reason I don't like Python!

I was recently writing some Python code on my Raspberry PI.
I got so frustrated I ended up re-writing in C.

--
Paul

[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/040901d2fc18$7155f8c0$5401ea40$@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Ted Roche]

On Thu, Jul 13, 2017 at 9:40 AM,
 wrote:
>
> It pays to take the time and do good modular design instead of this
> way-too-long PRG run on crap.  hahaha
>

So, wait, you're saying that if you create functions/modules/methods
that are short, do only one thing, having clearly defined input and
output ranges and values, can be tested in isolation, have clear entry
and exit points, have a consistent error handling, are orchestrated
together,...  in other words, good coding is easier to debug?

Hunh. I learn something new on this forum every day.


-- 
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com

___
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/CACW6n4sSxW7cioYFbhP3_PBq3=sfetmnqkxiyvrplvjhayn...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Kurt Wendt]

Hey  Paul - I think your reply is more in the way of Derailment instead of 
HiJacking!
:-)

I must admit - sometimes when I want a little break from work - I come hang out 
here in the land of ProFox - just for the entertainment value it affords me!

Regards,
Kurt Wendt
Senior Systems Analyst 


Tel. +1-212-747-9100
www.GlobeTax.com

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul H. 
Tarver
Sent: Thursday, July 13, 2017 4:14 PM
To: profoxt...@leafe.com
Subject: RE: "An IF | ELSE | ENDIF statement is missing"

Not to hijack this thread, but were you two talking about Monty and the errant 
for the Holy Grail? :)

Paul H. Tarver
Tarver Program Consultants, Inc.
Email: p...@tpcqpc.com


-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul Hill
Sent: Thursday, July 13, 2017 2:11 PM
To: profoxt...@leafe.com
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

On 13 July 2017 at 18:51, Malcolm Greene <pro...@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.

It makes it worse!  It's the number one reason I don't like Python!

I was recently writing some Python code on my Raspberry PI.
I got so frustrated I ended up re-writing in C.

--
Paul

[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/80838f1ca795b14ea1af48659f35166f19012...@drexch02.corp.globetax.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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Paul H. Tarver]

Not to hijack this thread, but were you two talking about Monty and the
errant for the Holy Grail? :)

Paul H. Tarver
Tarver Program Consultants, Inc.
Email: p...@tpcqpc.com


-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul
Hill
Sent: Thursday, July 13, 2017 2:11 PM
To: profoxt...@leafe.com
Subject: Re: "An IF | ELSE | ENDIF statement is missing"

On 13 July 2017 at 18:51, Malcolm Greene <pro...@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.

It makes it worse!  It's the number one reason I don't like Python!

I was recently writing some Python code on my Raspberry PI.
I got so frustrated I ended up re-writing in C.

--
Paul

[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/03fc01d2fc14$8728f700$957ae500$@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Paul Hill]

On 13 July 2017 at 18:51, Malcolm Greene  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.

It makes it worse!  It's the number one reason I don't like Python!

I was recently writing some Python code on my Raspberry PI.
I got so frustrated I ended up re-writing in C.

-- 
Paul

___
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/CADwx0+KXaxkBb0g_bE5u=1BD4S9G88xSmWqEFkOpx==f_jn...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[John Weller]

A technique I've used in the past for complex structures - definitely worth
the effort!

John Weller
01380 723235
07976 393631


> 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.


___
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/001a01d2fc0a$c4b95b00$4e2c1100$@johnweller.co.uk
** 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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Laurie Alvey]

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  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+5gfvwno1c7uvhpmpu...@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Malcolm Greene]

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.72511...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Michael Glassman]

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-boun...@leafe.com] On Behalf Of Laurie
Alvey
Sent: Thursday, July 13, 2017 11:32 AM
To: profoxt...@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 <p...@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: p...@tpcqpc.com
>
>
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of 
> mbsoftwaresoluti...@mbsoftwaresolutions.com
> Sent: Thursday, July 13, 2017 8:41 AM
> To: profoxt...@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.

Re: "An IF | ELSE | ENDIF statement is missing"

[Laurie Alvey]

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 <p...@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: p...@tpcqpc.com
>
>
> -Original Message-
> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
> mbsoftwaresoluti...@mbsoftwaresolutions.com
> Sent: Thursday, July 13, 2017 8:41 AM
> To: profoxt...@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=a...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Paul H. Tarver]

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: p...@tpcqpc.com 


-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Thursday, July 13, 2017 8:41 AM
To: profoxt...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Darren]

I could do that - not right now though - just on midnight here and about to
hit the hay. 

-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:57 PM
To: profoxt...@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!  ;-)

https://leafe.com/dls/vfp

[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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Darren]

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", 1)
  
  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", 1)
  
  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-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:41 PM
To: profoxt...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[mbsoftwaresolutions]

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!  ;-)


https://leafe.com/dls/vfp

___
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/244f21bf0be310b66b58f93917ed8...@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.

RE: "An IF | ELSE | ENDIF statement is missing"

[Darren]

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-boun...@leafe.com] On Behalf Of
mbsoftwaresoluti...@mbsoftwaresolutions.com
Sent: Thursday, 13 July 2017 11:41 PM
To: profoxt...@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.

"An IF | ELSE | ENDIF statement is missing"

[mbsoftwaresolutions]

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/5b3aaba876ba6d49dc5b61940945c...@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.