Re: Code problems with Perform Thru Exit causes fall through

On Jul 28, 12:03 pm, "tlmfru" <la...@xxxxxxx> wrote:

Man, don't start a religious style war again. SECTIONS are never necessary,
so far as I know, but can be used perfectly effectively.

Evrybody has a verb or two that they dislike. Who cares???? Does it work?
Is it easy to maintain?

SECTIONs do have their uses, for example segmentation. As I pointed
out above I dislike things that can easily lead to errors and that the
compiler won't tell you about. In fact I would use that as a
definition of what is _not_ 'easy to maintain' and _not_ 'perfectly
effective'.

For example (as above) the simple absence of one SECTION word on a
label can cause a drop thru error that can be difficult to locate and
which the compiler gives no warning of.

The only purpose for using PERFORMed SECTIONs instead of having all
the labels as paragraphs is to allow the use of exit paragraphs and
the associated GO TOs. Thus this style suffers the errors in my other
messages of this topic, ones that the compiler cannot find for you.

Perhaps you find that these errors are simply a part of 'normal
programming' and find them easy, after all what would you do for the
rest of the week if they did not occur.

Does it follow the installation standards?
Discussion over!

Yes, that is often used to protect poor programming styles.


.

Relevant Pages

  • Re: Problems compiling a lambda expression
    ... The problem is that the compiler seems to dislike ... But without knowing the error, it's hard to say for sure which or whether either is correct. ... I don't see anything obviously wrong with the lambda expression, but again...if you're not using C# 3.0, then it wouldn't work. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: C closures & lexical scoping
    ... runtime calls, and other things, whenever we use certain language ... Why do you think people tend to dislike it, and why do you think it's an uncommon feature of C compilers? ... Whether it's better to implement a feature using a function call or by inlining the code that would otherwise be in such a function is precisely the kind of optimizing detail that I want the compiler to worry about, ...
    (comp.lang.c)