[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

elseif v. elsif ??

7stud 7stud

3/7/2007 8:57:00 AM

What the?? I just spent two days trying to figure out why I couldn't
reproduce the example in "Ruby in 20 minutes" and get it to work. After
examining my code line for line against the example code and not being
able to detect any error, I was assembling several code examples into a
text file to post here, when I happened to notice 'elsif'. Why
didn't Ruby flag 'elseif' as an error?


Does Ruby try differentiate itself in ridiculous ways like that just for
the sake of being different? And why isn't something like that
explicitly pointed out in a beginning tutorial? So far, I have to give
Ruby two thumbs down.

C++, Java, Javascript, php, Servlets+JSP programmer

--
Posted via http://www.ruby-....

82 Answers

Chad Perrin

3/7/2007 9:00:00 AM

0

On Wed, Mar 07, 2007 at 05:56:56PM +0900, 7stud 7stud wrote:
>
> Does Ruby try differentiate itself in ridiculous ways like that just for
> the sake of being different? And why isn't something like that
> explicitly pointed out in a beginning tutorial? So far, I have to give
> Ruby two thumbs down.

Ruby isn't the only language that does that.

"Different" would be more like the way bash does it: "elif"

--
CCD CopyWrite Chad Perrin [ http://ccd.ap... ]
"There comes a time in the history of any project when it becomes necessary
to shoot the engineers and begin production." - MacUser, November 1990

Robert Dober

3/7/2007 9:04:00 AM

0

On 3/7/07, 7stud 7stud <dolgun@excite.com> wrote:
> What the?? I just spent two days trying to figure out why I couldn't
> reproduce the example in "Ruby in 20 minutes" and get it to work. After
> examining my code line for line against the example code and not being
> able to detect any error, I was assembling several code examples into a
> text file to post here, when I happened to notice 'elsif'. Why
> didn't Ruby flag 'elseif' as an error?
Because it nvere sees it :(

Look at two examples

if true then
whatever
elseif
end

now elsif is seen as an undefined method but

if false then
whatever
elseif
end

whatever and elseif are not evaluated.

I strongly advice you to use a syntax highlighting ediotr like e.g.
vim, emacs, Jedit, geany and tons of others.

Cheers
Robert
>
>
> Does Ruby try differentiate itself in ridiculous ways like that just for
> the sake of being different? And why isn't something like that
> explicitly pointed out in a beginning tutorial? So far, I have to give
> Ruby two thumbs down.
>
> C++, Java, Javascript, php, Servlets+JSP programmer
>
> --
> Posted via http://www.ruby-....
>
>


--
We have not succeeded in answering all of our questions.
In fact, in some ways, we are more confused than ever.
But we feel we are confused on a higher level and about more important things.
-Anonymous

Hans Sjunnesson

3/7/2007 9:20:00 AM

0

On Mar 7, 9:56 am, 7stud 7stud <dol...@excite.com> wrote:
> What the?? I just spent two days trying to figure out why I couldn't
> reproduce the example in "Ruby in 20 minutes" and get it to work. After
> examining my code line for line against the example code and not being
> able to detect any error, I was assembling several code examples into a
> text file to post here, when I happened to notice 'elsif'. Why
> didn't Ruby flag 'elseif' as an error?
>
> Does Ruby try differentiate itself in ridiculous ways like that just for
> the sake of being different? And why isn't something like that
> explicitly pointed out in a beginning tutorial? So far, I have to give
> Ruby two thumbs down.
>
> C++, Java, Javascript, php, Servlets+JSP programmer
>
> --
> Posted viahttp://www.ruby-....

Well, Ruby doesn't try to differentiate itself in ridiculous ways just
for the sake of being different. It's not a person.
However, it will spit out a "undefined method 'elseif' for main:Object
(NoMethodError)" when you use 'elseif', so it's really not a problem
is it?

--
Hans

Stefano Crocco

3/7/2007 9:36:00 AM

0

Alle mercoledì 7 marzo 2007, Robert Dober ha scritto:
> if true then
>    whatever
>    elseif
> end
>
> now elsif is seen as an undefined method but

Not always. In Robert's first example,

> if true then
> whatever
> elseif
> end

you'll get a NameError (undefined local variable or method `elseif' for
main:Object (NameError))

In the following example, instead, you get a syntax error:

if x < 0 then puts "x<0"
elseif x < 3 then puts "0<=x<3"
else puts "x>=3"
end

The error message is:

syntax error, unexpected kTHEN, expecting kEND
elseif x < 3 then puts "0<=x<3"
^
Here, ruby doesn't complain because elseif doesn't exist, but because it finds
a 'then' where it shouldn't be (not following an if or elsif clause). By the
way, being a syntax error (it when the interpreter is parsing the file, not
when it executes it), this error is reported whatever the value of x is (and
even if x doesn't exist).

All these error messages aren't very easy to understand for a novice. To make
a comparison with other programming languages, I tried compiling a C program
with a similar mistake (in this case writing 'elseif' instead of 'else if').
The program was:

int main(){
int a=3;
int b=0;
if( a==4){ b=1;}
elseif(a==2){ b=2;} //should be else if
else{ b=3;}}
}

Compiling with gcc, the error message I got is:

test.c: In function 'main':
test.c:5: error: expected ';' before '{' token

As you can see, the error message doesn't speak of invalid keywords, but just
of a missing ;

Stefano

Robert Dober

3/7/2007 9:37:00 AM

0

On 3/7/07, Hans Sjunnesson <hans.sjunnesson@gmail.com> wrote:
> On Mar 7, 9:56 am, 7stud 7stud <dol...@excite.com> wrote:
> > What the?? I just spent two days trying to figure out why I couldn't
> > reproduce the example in "Ruby in 20 minutes" and get it to work. After
> > examining my code line for line against the example code and not being
> > able to detect any error, I was assembling several code examples into a
> > text file to post here, when I happened to notice 'elsif'. Why
> > didn't Ruby flag 'elseif' as an error?
> >
> > Does Ruby try differentiate itself in ridiculous ways like that just for
> > the sake of being different? And why isn't something like that
> > explicitly pointed out in a beginning tutorial? So far, I have to give
> > Ruby two thumbs down.
> >
> > C++, Java, Javascript, php, Servlets+JSP programmer
> >
> > --
> > Posted viahttp://www.ruby-....
>
> Well, Ruby doesn't try to differentiate itself in ridiculous ways just
> for the sake of being different. It's not a person.
> However, it will spit out a "undefined method 'elseif' for main:Object
> (NoMethodError)" when you use 'elseif', so it's really not a problem
> is it?
>
> --
> Hans
>
>
>
No of course it is not :)
I think to understand the frustration of OP however.
He is probably coming from a completely different world and it is not
always easy to grasp new concepts.
Therefore I preferred to ignore the aggressive nature of the post ;).
He might even have a point when he says that this is maybe not really
well documented, With this I do not mean the "elseif" of course but
just the dynamic evaluation of the code.

Maybe a chapter for that kind of pitfalls could be added somewhere -
well it probably is already, maybe somebody can indicate that.

This is however not a clearcut thing as it might seem at first view.

Robert


--
We have not succeeded in answering all of our questions.
In fact, in some ways, we are more confused than ever.
But we feel we are confused on a higher level and about more important things.
-Anonymous

Chris Lowis

3/7/2007 9:59:00 AM

0

> Maybe a chapter for that kind of pitfalls could be added somewhere -
> well it probably is already, maybe somebody can indicate that.

Perhaps at the "Ruby from other languages" page :
http://www.ruby-lang.org/en/documentation/ruby-from-other-...

I find this page very helpful.

Regards,


Chris

--
Posted via http://www.ruby-....

Robert Dober

3/7/2007 10:30:00 AM

0

On 3/7/07, Stefano Crocco <stefano.crocco@alice.it> wrote:
<snip>

Good points Stefano, conclusion *always* use "then" :)
--
We have not succeeded in answering all of our questions.
In fact, in some ways, we are more confused than ever.
But we feel we are confused on a higher level and about more important things.
-Anonymous

7stud 7stud

3/7/2007 10:54:00 AM

0

Chris Lowis wrote:
>> Maybe a chapter for that kind of pitfalls could be added somewhere -
>> well it probably is already, maybe somebody can indicate that.
>
> Perhaps at the "Ruby from other languages" page :
> http://www.ruby-lang.org/en/documentation/ruby-from-other-...
>
> I find this page very helpful.
>
> Regards,
>
>
> Chris


First, I'd like to say that the web site is really beautiful and eye
catching. There are some minor problems, for instance, the code
examples are in a small area width wise, so there is a horizontal scroll
bar that you need to scroll to the right to see the latter portion of a
line of code. However, the area with the code is very tall(more than
one screen), and it is very inconvenient to page all the way down to the
bottom in order to scroll to the right, and then go all the way back up
in order to read the code. Also, no matter how wide I make my browser
window(Safari 2.0.4), the area with the code does not expand
horizontally. It should expand horizontally as the browser window gets
wider, and the horizontal scroll bars should disappear.

If I run the following code, I don't get any errors:

class MegaGreeter
attr_accessor :names

#constructor
def initialize(names = "world")
@names = names
end

#functions:
def say_hi
if @names.nil?
puts "..."
elseif @names.respond_to?("each")
@names.each do |name|
puts "Hello #{name}!"
end
else
puts "Hello #{@names}!"
end
end
end
if __FILE__ == $0
mg = MegaGreeter.new(["Sally", "Jane", "Bob"])
mg.say_hi
end


--
Posted via http://www.ruby-....

7stud 7stud

3/7/2007 10:58:00 AM

0

My output is:

~/2testing/dir1$ ruby rubyHelloWorld.rb
Hello SallyJaneBob!

ruby version:

~/2testing/dir1$ ruby -v
ruby 1.8.2 (2004-12-25) [universal-darwin8.0]

--
Posted via http://www.ruby-....

Brian Candler

3/7/2007 11:02:00 AM

0

On Wed, Mar 07, 2007 at 07:54:15PM +0900, 7stud 7stud wrote:
> If I run the following code, I don't get any errors:
>
> class MegaGreeter
> attr_accessor :names
>
> #constructor
> def initialize(names = "world")
> @names = names
> end
>
> #functions:
> def say_hi
> if @names.nil?
> puts "..."
> elseif @names.respond_to?("each")
> @names.each do |name|
> puts "Hello #{name}!"
> end
> else
> puts "Hello #{@names}!"
> end
> end
> end
> if __FILE__ == $0
> mg = MegaGreeter.new(["Sally", "Jane", "Bob"])
> mg.say_hi
> end

That's because you're not exercising the section under @names.nil?

Try: mg = MegaGreeter.new(nil)