The Daily Static
  The Daily Static
UF Archives
Register
UF Membership
Ad Free Site
Postcards
Community

Geekfinder
UFie Gear
Advertise on UF

Forum Rules
& FAQ


Username

Password


Create a New Account

 
 

Back to UserFriendly Strip Comments Index

goto by perldude2002-06-11 09:00:28
  There are several cases where goto is appropriate. by Yohimbe2002-06-11 09:19:09
    Yep. KnR said so themselves... by Tars_Tarkas2002-06-11 09:30:33
      in which case... by Epiphany02002-06-11 09:36:39
        But how for multiple nested loops? by Freakazoid2002-06-11 09:39:08
          then... by Epiphany02002-06-11 09:45:54
            It ultimately obfuscates the structure... by HadEnuf2002-06-11 09:59:44
              Would you call java's exception handling by Yohimbe2002-06-11 10:02:09
                It's at least an incremental improvement... by HadEnuf2002-06-11 10:10:14
                  How about continuations? by Schol-R-LEA;2 2006-11-19 12:55:59
These have been a bone of contention in the LISP, ML, Smalltalk and Python worlds for years. some hold them as a superior solution to the issue of resolving deep nesting, as well as a mechanism to build exception handling around. Others see them as a crock that only exacerbates the problem. If you're familiar with them, what do you think?

For more information, see Continuations made Simple (with examples in Python), Searching an Explanation: call/cc and 'do' Strangeness (part of a discussion thread), Continuations and Stackless Python, Applications for Continuations, An Introduction to Scheme (a series of slides from a lecture; not very useful, but it does illustrate the use of continuations for exception handling), or An Introduction to Scheme and its Implementation.

(I must admit, I haven't used them and don't fully understand them, myself, so I haven't formed any solid opinions myself. It does seem to be an elegant method in the formal sense, but a very confusing one in practice.)
[ Reply ]

 

[Todays Cartoon Discussion] [News Index]

Come get yer ARS (Account Registration System) Source Code here!
All images, characters, content and text are copyrighted and trademarks of J.D. Frazer except where other ownership applies. Don't do bad things, we have lawyers.
UserFriendly.Org and its operators are not liable for comments or content posted by its visitors, and will cheerfully assist the lawful authorities in hunting down script-kiddies, spammers and other net scum. And if you're really bad, we'll call your mom. (We're not kidding, we've done it before.)