[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GOP2-3 - GLISS or not
From: |
Graham Percival |
Subject: |
Re: GOP2-3 - GLISS or not |
Date: |
Thu, 26 Jul 2012 09:37:20 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Jul 26, 2012 at 09:02:38AM +0100, Trevor Daniels wrote:
> Graham Percival wrote Tuesday, July 24, 2012 10:09 AM
>
> > Let’s decide whether to try to stabilize the syntax or not.
>
> We /should/ try to stabilize the syntax, but trying to do this
> at exactly the time when David is straightening out the
> parser seems a bad idea. As yet we do not know where
> the parser changes may lead eventually.
tl;dr: we agree on the actual "what we will do", but disagree on
the reasons behind it. :)
I actually think that David's work on the parser makes this is the
perfect time to do GLISS.
- the code should match our desired language specification, not
the other way around. Do we want to allow numbers like 0.37
which do not begin with a leading 0? that's not a code
question, that's a language question. Of course the language
design should be heavily influenced by the implications for
the computer implementation (i.e. parser and lexer), so I
don't think we would be able to have this discussion
without David's expertise on the matter.
- straightening out the parser is going to lead to some breakage
in (complicated and/or badly written) scores. That may lead
to some understandable frustration from some users, but if
we're running GLISS at the same time, that gives them some
hope that things will settle down.
> I'd be happy to see a start being made on this now, in spite
> of my comments above, but we must delay the actual
> release of the definitive syntax-stable version until we have
> confidence the parser changes have stabilized. The task David
> has set himself is difficult enough without his being hamstrung
> by a premature release imposing further constraints on the
> parser. Predicting the effect those constraints might have
> on the parser is pretty well impossible.
I agree with delaying the definitive syntax-stable versions; I'm
imagining something like a "proposed stable" syntax that must
exist for 6 or 12 months without any change or quibbles before
it's accepted as "actually stable".
- Graham
- Re: GOP2-3 - GLISS or not, (continued)
Re: GOP2-3 - GLISS or not, Ian Hulin, 2012/07/24
Re: GOP2-3 - GLISS or not, Nicolas Sceaux, 2012/07/24
Re: GOP2-3 - GLISS or not, Andrew Hawryluk, 2012/07/25
Re: GOP2-3 - GLISS or not, Keith OHara, 2012/07/25
Re: GOP2-3 - GLISS or not, Trevor Daniels, 2012/07/26
Re: GOP2-3 - GLISS or not, Joseph Rushton Wakeling, 2012/07/26
- Re: GOP2-3 - GLISS or not, David Kastrup, 2012/07/26
- Re: GOP2-3 - GLISS or not, Joseph Rushton Wakeling, 2012/07/26
- Re: GOP2-3 - GLISS or not, Graham Percival, 2012/07/26
- Re: GOP2-3 - GLISS or not, Joseph Rushton Wakeling, 2012/07/27
- Re: GOP2-3 - GLISS or not, Graham Percival, 2012/07/27
- Re: GOP2-3 - GLISS or not, Joseph Rushton Wakeling, 2012/07/27
- Re: GOP2-3 - GLISS or not, Werner LEMBERG, 2012/07/28
- Re: GOP2-3 - GLISS or not, David Kastrup, 2012/07/28