Hi Bill.

> I can certainly wait a few more days to do another build. I might have a 
> few minor things to check in anyway.

Ok. I believe that I have now successfully fixed the type-checker issue.

> As a side note, it's probably worth mentioning that I'm not opposed to 
> doing 7.8 releases on a more frequent basis; in fact, I'd almost prefer to 
> do a quarterly release rather than prepare an ongoing series of betas. I 
> say this not only because it's been so long since an official release, but 
> also because I feel as though people lose interest in looking at betas if 
> they don't see a light (release) at the end of the tunnel.

Agreed.

> Or, put another way: once we're rolling toward what would otherwise be an 
> official release, I don't think that fixing a bug alone is reason enough 
> to cut a new beta, unless it's a regression. Of course, that's assuming 
> that one can count on the fix going out in a timely next release (which 
> is a situation I'd like to get back to).

The issue I just fixed could be triggered by some of the standard
modules (depending on C-compiler and context) and caused the compiler
to SEGV due to running out of C-stack. I believe that SEGV bugs are
critical enough to hold up a release. Otherwise I certainly agree that
we should attempt to release quite a bit more often.

        /grubba
  • Re: New Pike Bet... Arne Goedeke
    • Re: New Pik... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
      • Re: New... Arne Goedeke
        • Re:... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
          • ... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
  • New Pike Beta: 7... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
    • Re: New Pik... H. William Welliver III
      • Re: New... Martin Bähr
        • Re:... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
          • ... Bill Welliver
            • ... Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
              • ... Bill Welliver

Reply via email to