Re: New switch/case idea

new topic     » goto parent     » topic index » view thread      » older message » newer message
Mike777 said...

Well, I can't argue with the fact that a break can potentially change the logic flow. If that is the only criteria for disallowing it in this circumstance, I feel the argument is fairly weak. If there is one area where Euphoria does not shine it is in the area of debugging, so I would err on the side of aiding that effort, even if it allowed me some rope that I *might* end up hanging myself with.

Encasing a short bit of code in a block comment is not a problem.

But just like the comment I made a few posts ago, don't confuse these short examples for real-world programs. I might have a SWITCH (or any other logic selection statement) associated with blocks of code that are multiple-screens long. And I might have 30 of them, rather than just one or two. And if you force me to find both the top and the bottom of each section, to insert the block comment indicators (or remove them), I promise you I will instead use the GOTO construct.

I would argue the larger the switch gets the more complex "break" for a debug construct gets. BTW... In Euphoria's source code, we have switches that are > 200 case statements long.

Jeremy

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu