From: Timothy Gregory Date: 2013-02-18T01:40:31+09:00 Subject: Re: so, what's the proper way to replace funcionality of GOTO ? --047d7b6d88b268671d04d5ee4027 Content-Type: text/plain; charset=ISO-8859-1 i recall the Amiga thrived on tons of GOTO 's thrashed to the point where it was almost every third word on the page there is a bunch of goto's in ruby-parse.y lines 10203-10250 on github parse.y#L10203 On Sat, Feb 16, 2013 at 4:49 AM, WILLS, JAMAL A wrote: > I think GOTO gets a bad rap. Actually, I find the COMEFROM command far > more terrifying. It's mentioned in the comments... > > Jamal > > -----Original Message----- > From: Ryan Victory [mailto:ryan@raptormail.net] > Sent: Friday, February 15, 2013 12:03 PM > To: ruby-talk ML > Subject: Re: so, what's the proper way to replace funcionality of GOTO ? > > I did consider jokingly showing the "enable jokes" compiler flag that > turned on the __goto__ method...I'm actually slightly horrified that > Ruby has anything resembling goto for hopping around in code. I'll > concede that I did not know about this, however I'll stand by the idea > that it's terrible coding practice (except for in very particular > circumstances where goto is the most elegant solution). > > Either way, your original suggestion is just bad advice. I'll stand by > that. > > -Ryan > On 2/15/13 10:56 AM, Love U Ruby wrote: > > Ryan Victory wrote in post #1097114: > >> Love U Ruby: I'm really not sure what you meant by that response, but > >> it's irrelevant and inaccurate (there is no catch in Ruby, it's > >> rescue)... > >> > > before going to challenge other you should "GOOGLE" - here I did for > > you. > > > > Please read it : http://www.devalot.com/articles/2012/03/ruby-goto > > > > > --047d7b6d88b268671d04d5ee4027 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

i recall the Amiga thrived on tons of GOTO 's thrashed to the point where it was almost every third word on the page
=

there is a bunch of goto's in ruby-parse.y lines 10203-10250 = on github
parse.y#= L10203

On Sat, Feb 16, 2013 at 4:49 AM, WILLS, JAMAL A &l= t;jw1496@att.com>= ; wrote:

I think GOTO gets a bad rap. =A0Actually, I = find the COMEFROM command far more terrifying. =A0It's mentioned in the= comments...

Jamal

-----Original Message-----
From: Ryan Victory [mailto:ryan@rapt= ormail.net]
Sent: Friday, February 15, 2013 12:03 PM
To: ruby-talk ML
Subject: Re: so, what's the proper way to replace funcionality of GOTO = ?

I did consider jokingly showing the "enable jokes" compiler flag = that
turned on the __goto__ method...I'm actually slightly horrified that Ruby has anything resembling goto for hopping around in code. I'll
concede that I did not know about this, however I'll stand by the idea<= br> that it's terrible coding practice (except for in very particular
circumstances where goto is the most elegant solution).

Either way, your original suggestion is just bad advice. I'll stand by = that.

-Ryan
On 2/15/13 10:56 AM, Love U Ruby wrote:
> Ryan Victory wrote in post #1097114:
>> Love U Ruby: I'm really not sure what you meant by that respon= se, but
>> it's irrelevant and inaccurate (there is no catch in Ruby, it&= #39;s
>> rescue)...
>>
> before going to challenge other you should "GOOGLE" - here I= did for
> you.
>
> Please read it : =A0http://www.devalot.com/articles/2012/03/ruby-= goto
>

--047d7b6d88b268671d04d5ee4027--