But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end

As far as I can tell there is no way in Ruby to use .each or .times to
go backwards.

While I realize this thread is about the ++ operator the
-- operator is complementary.

snip

Walton Hoops wrote:
-----Original Message-----
From: marnen at (no spam) marnen.org [mailto:marnen at (no spam) marnen.org]
Now consider the ruby way:

10.times do |i|
print "#{i},"
end

Some length as the C code, but much more readable. Heck, it's
almost English!

But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end
As far as I can tell there is no way in Ruby to use .each or .times to go
backwards. While I realize this thread is about the ++ operator the --
operator is complementary.

Michael W. Ryder wrote:
[...]
But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end

No.

10.downto(1) do |i|
puts i
end

As far as I can tell there is no way in Ruby to use .each or .times to
go backwards.

That's what .downto is for. (Have you ever needed this? I have not.)

Oh, I have no problem with ++ per se. It just seems against the grain
in Ruby.

Michael W. Ryder wrote:
[...]
But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end

No.

10.downto(1) do |i|
puts i
end

As far as I can tell there is no way in Ruby to use .each or .times to
go backwards.

That's what .downto is for. (Have you ever needed this? I have not.)

While I realize this thread is about the ++ operator the
-- operator is complementary.

snip

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
marnen at (no spam) marnen.org

Marnen Laibow-Koser wrote:
Michael W. Ryder wrote:
[...]
But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end

No.

10.downto(1) do |i|
puts i
end

As far as I can tell there is no way in Ruby to use .each or .times to
go backwards.

That's what .downto is for. (Have you ever needed this? I have not.)


I missed the downto method, I guess that is a problem when you have so many
different ways to do the same basic things. I much prefer the simplicity of
Basic and C with for loops that can go either direction. As far as going
backwards I use it a lot to parse strings of the form "city name ST
12345-6789" to City, State, and Zip Code fields. I look for the first blank
from the end of the string and assume everything after it is the Zip Code, I
then find the next two non-blank characters and assign them to State, and
everything else is the City name.

-----Original Message-----
From: Michael W. Ryder [mailto:_mwryder55 at (no spam) gmail.com]
But if you wanted to do something like:
i = 10;
while (i > 0)
{
printf("%d/n", i--);
}
in Ruby you would have to do something like:
i = 10
while (i > 0)
puts i
i -= 1
end
As far as I can tell there is no way in Ruby to use .each or .times to
go backwards. While I realize this thread is about the ++ operator the
-- operator is complementary.

. I much prefer the
simplicity of Basic and C with for loops that can go either direction.

As far as going backwards I use it a lot to parse strings of the form
"city name ST 12345-6789" to City, State, and Zip Code fields. I look
for the first blank from the end of the string and assume everything
after it is the Zip Code, I then find the next two non-blank characters
and assign them to State, and everything else is the City name.

On Sun, Nov 8, 2009 at 12:32 PM, Tony Arcieri <t... at (no spam) medioh.com> wrote:
I cannot begin to answer this question because Ruby is doing strange and
unexpected things here, at least from my perspective...

Never mind, bar= was still defined because I was reopening the class.

Gaah, close this thread! ;)

I suppose the whole discussion is moot as Ruby will likely never see a ++
operator.

I was just trying to make clear the limitation wasn't a technical one, and
further show how a ++ operator could be "Ruby-like" while still retaining
C/C++/Java-like semantics.

On Sun, Nov 8, 2009 at 2:30 PM, Florian Aßmann
florian.assmann at (no spam) email.de>wrote:

Gaah, close this thread! ;)


I suppose the whole discussion is moot as Ruby will likely never see a
++
operator.

I was just trying to make clear the limitation wasn't a technical one,
and
further show how a ++ operator could be "Ruby-like" while still
retaining
C/C++/Java-like semantics.

Dude, you just about gave me a heart attack. Phewsh - sanity is
restored.

BTW in all your posts on the topic, you don't seem to address pre-
increment vs post-incrememt. (Forgive me if I'm wrong.) If Ruby
implemented ++ and didn't address that, it wouldn't be C or C++
semantics at all.


That's a can of worms I've been trying to avoid, as there are lexing/parsing
ambiguities surrounding the combination of both. How do you parse a+++b vs
a++++b vs a+++++b?

If implementing ++ requires changes to the parser, that seems like a
pretty technical limitation to me! :)

BTW in all your posts on the topic, you don't seem to address pre-
increment vs post-incrememt. (Forgive me if I'm wrong.) If Ruby
implemented ++ and didn't address that, it wouldn't be C or C++
semantics at all.