That's ace!
In Emacs it can actually be one level neater; since the tests are run from within Emacs itself it's easy to simply set the env var before kicking off the test run. No need to edit the source file.
Let's say there's a class with quite a few different tests and I'm currently TDD-ing this single method.
sub ion_favourites : Test(no_plan) {
#...
}
What is the plan (if any) wrt machine readable Perl6?
Would syntax highlighting be done with regexes and duct tape, or are there some kind of introspection available/planned for IDEs?
I can only remember reading a few years ago that there was an idea to let Perl parse source and emit structural information suitable for syntax highlighting, navigation and so on, but I haven't heard anything in this area since.
Is the Office suite installed?
(This is just out of curiosity, I probably wouldn't do any Win32::Word::Writer development regardless)
Let me just second that.
I don't think that's configurable since it's a bit of a special case to only want to indent one of the structures.
Unfortunately Perl::Tidy doesn't seem to have any tests to speak of, so it's a bit of an effort to start hacking on it to add missing bits.
There is an old strawberry installer linked from the the wiki. Is there a more recent one that installs it an all deps easily? (esp the GTK things are a bit tricky IIRC)
For being from -95, that's not too bad.
Just using the then-not-yet-a-pattern of listing all sections (well, pages in this case) and highlighting the current makes it stand out somewhat.
Why include UNIVERSAL in the diagram?
Its presence doesn't clarify anything. The only thing it does is make the graph more difficult to read.
What if you suddenly wake up an realize you have a large volume of duplicated test code (which may be the case, I have no idea)? Wouldn't you want to schedule time to make a serious difference?
I think the presence of a card is a very un-sad thing for various reasons (they identified the problem, took action, got on scheduled time for it).
So it seems the Ruby community is following along in the same footsteps as Perl, just a few years later. From experiencing the perils of AUTOLOAD and monkey patching to doing stupid things like porn references at conferences.
Well, from what I've seen they'll never catch up on the last one.
I'm saying the bug had nothing to do with MI.
My reply was referring to the last paragraph about the bug, not the whole post. Reading the reply again, I can see that wasn't clear.
This had nothing to do with multiple inheritance. At all.
The problem was it wasn't a pure refactoring. It added functionality to a class (which was appropriate), and the setup code for the failing test wasn't amended to reflect this.
