Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I've never quite understood the RSpec crowd's obsession with renaming things, but as a library RSpec kicks the default ruby Test::Unit's arse so comprehensively otherwise.

    Nor do I understand the style that has them use do ... end style 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
    • I really, really, really hate that extraneous fscking 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 do

      But, hey, ruby pays my mortgage and I'll swap the aesthetic pain
      • So that means you'll be back to Perl 5 if 5.12 has named parameters to subs and/or methods? ;)
        • Probably not. See the comment about the mortgage.

          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.