NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Calm down dear, it's only programming (Score:1)
Nor do I understand the style that has them use
do ... endstyle blocks to wrap code that, at it's best looks declarative. It's not impossible to write:describe SomeClass {
it "should be instantiable" {
SomeClass.new.should_not be_nil
}
}
which seems a good deal cleaner. Many ruby progr
Or to put it another way (Score:1)
do. If only the language would let me declare things so I could write:describe Something
it "should do stuff"
do_stuff_with_it
end
end
I'd be a good deal happier. Yes, I could write a source filter type thing in the runner, but I don't want the pain of having to parse the whole of the rest of bloody ruby just to get rid of that stupid
doBut, hey, ruby pays my mortgage and I'll swap the aesthetic pain
Re: (Score:1)
Re: (Score:1)
I'm holding out for malleable syntax, real objects, proper garbage collection and decent function/method prototypes.
And a fanatical devotion to the Pope.
It's more likely to be things like DateTime that lure me back - Ruby's date handling is woeful.
Re:Or to put it another way (Score:2)
Reply to This
Parent
Re: (Score:1)
1.month.from_nowby inventing/rediscovering the Duration class.http://www.perl.com/pub/a/2003/03/13/datetime.html [perl.com] is a good read too, in which Dave Rolsky explains the issues with the ad hoc nature of most Perl calendrical modules before the DateTime better