parse-info branch ready for merging?



>>>>> "Rupert" == Rupert Swarbrick <rswarbrick at gmail.com> writes:

    Rupert> I *think* that the parse-info branch is now ready for merging.
    Rupert> Things that have changed recently:

Before merging, I think you should give people a couple of weeks for
testing with the latest code.  (Might seem like a long time, but we're
all volunteers.)

    Rupert> This *hasn't* been tested on Windows. So is there any chance someone
    Rupert> could give it a go? (I don't have a Windows machine to test on, I'm
    Rupert> afraid) Provided things work sensibly there, I think the master branch
    Rupert> will now be improved by merging in parse-info.

Without testing on Windows, I would have to vote no on merging,
unfortunately.

I wish there were a way to say at runtime to use the new parse-info
way or the old way, in case we find issues.  But that might be more
effort than it's worth.  And IIRC the changes are fairly large so if
we do find issues, reverting the parse-info merge may be somewhat
difficult.

Ray