Re: interesting use of NEXT SENTENCE vs. CONTINUE
- From: docdwarf@xxxxxxxxx
- Date: 3 Jun 2005 05:27:23 -0400
In article <1117765632.634020.104870@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Richard <riplin@xxxxxxxxxxxx> wrote:
>
>docdwarf@xxxxxxxxx wrote:
>
>> >the very next full stop.
>>
>> >There is no indication at that point
>
>> Eh? The NEXT SENTENCE is the indication, at that point,
>
>If you follow the usual rules of english you should find that 'that
>point' refers to 'the very next full stop'.
Given the original construct of:
--begin quoted text:
The problem with NEXT SENTENCE, when combined with scope terminators,
is that it can be thought of a GO TO to an anonymous label formed by
the very next full stop. There is no indication at that point that the
full stop is the target of a logic path, nor, more importantly, that an
inserted full stop would become a new target of the path.
--end quoted text
.... it appears the phrase 'at that point' can have the preceding 'NEXT
SENTENCE' as its subject. Consider:
The problem with putting your shoes on is that it can be thought of as a
decision based in insufficient dara regarding the day's activities. There
is no indication at that point whether one will wind up doing (x), (y) or
(z).
But thanks for the clarification.
>
>When looking at a section of code that has a full stop in it there is
>no indication that this full stop is the target of a NEXT SENTENCE that
>is buried in the code at some point above this.
When you are looking at a paragraph there is no indication that the label
is the target of fall-through code, a PERFORM, a GO TO or a GO TO
DEPENDING ON; zealous advocating of these constructs has been called a
source for 'religious wars'.
My apologies if I have trodden unknowingly on your faith... but I,
personally, believe that code is to be read in context; I would say that
trying to fix code that is not read in context is more of a bug-trap than
any NEXT SENTENCE construction with which I am familiar... but I am, of
course, a man of limited experience.
>
>The only way to resolve how the logic works is to search the whole
>program, or at least all the program above the code you are examining.
See above about context.
>
>If an additional full-stop had been inserted in the code between 'that
>point' and the NEXT SENTENCE above it then there is no mechanism to
>resolve if this was an accidental change in logic or a deliberate one.
There is no mechanism of which I am aware that insures accurate repairs in
fractionally-understood code... or in completely-understood code, for that
matter.
DD
.
- Follow-Ups:
- Re: interesting use of NEXT SENTENCE vs. CONTINUE
- From: Richard
- Re: interesting use of NEXT SENTENCE vs. CONTINUE
- References:
- interesting use of NEXT SENTENCE vs. CONTINUE
- From: Frank Swarbrick
- Re: interesting use of NEXT SENTENCE vs. CONTINUE
- From: Richard
- Re: interesting use of NEXT SENTENCE vs. CONTINUE
- From: docdwarf
- Re: interesting use of NEXT SENTENCE vs. CONTINUE
- From: Richard
- interesting use of NEXT SENTENCE vs. CONTINUE
- Prev by Date: Re: rmcobol
- Next by Date: Re: RANDOM vs. DYNAMIC on indexed output file
- Previous by thread: Re: interesting use of NEXT SENTENCE vs. CONTINUE
- Next by thread: Re: interesting use of NEXT SENTENCE vs. CONTINUE
- Index(es):
Relevant Pages
|