Hi,
Ruby cannot simulate this behavior.
You are trying to force ruby to become what you know, instead of
learning
ruby’s different methods of doing the same thing.
The ‘def raise(*args)…’ solution given is pretty much what you want,
and if you want it clobal then $ignore_errors = 1. That it’s syntax is
different than VBs is a nonissue… If you want VB, stick with VB, don’t
turn ruby into VB.
Couldn’t agree more.
No, This routine does NOT have the same effect as in VB. Anyway, I’m a
pragmatic programmer. Don’t be ruby partisan… Cool down… I like ruby, I
learn it… Don’t fight a war of holy languages.
Thanks
Shannon.
···
Tired of spam? Get advanced junk mail protection with MSN 8.
http://join.msn.com/?page=features/junkmail
Hi,
Ruby cannot simulate this behavior.
You are trying to force ruby to become what you know, instead of
learning
ruby’s different methods of doing the same thing.
The ‘def raise(*args)…’ solution given is pretty much what you want,
and if you want it clobal then $ignore_errors = 1. That it’s syntax is
different than VBs is a nonissue… If you want VB, stick with VB, don’t
turn ruby into VB.
Couldn’t agree more.
No, This routine does NOT have the same effect as in VB. Anyway, I’m a
pragmatic programmer. Don’t be ruby partisan… Cool down… I like ruby, I
learn it… Don’t fight a war of holy languages.
Don’t worry, you’ll very rarely see any holy wars on this list. And people
generally aren’t Ruby partisan (not in a bad way, anyway). When people say
“Don’t try to do VB in Ruby” they’re not saying that the Ruby way is better
than the VB way (necessarily), but that it’s pointless trying to do VB in Ruby,
whatever its merits. That much is common sense, but everybody needs reminding
of it sometimes.
Anyway, you’ve generated quite an interest in the issue, so I’m sure we’d all
like to see how you’ve solved it.
Cheers,
Gavin
···
From: “Shannon Fang” xrfang@hotmail.com