On Sat, 28 Apr 2007 02:50:38 +0200, Leonardo Santagada
[EMAIL PROTECTED] wrote:
Now about semicolons, how should I deal with them? in the spec the
grammar doesn't deal with them and in the mozilla one I don't see
how they are doing it also. As we have set that as the parsing
module works
Florian Schulze wrote:
On Sat, 28 Apr 2007 02:50:38 +0200, Leonardo Santagada
[EMAIL PROTECTED] wrote:
Now about semicolons, how should I deal with them? in the spec the
grammar doesn't deal with them and in the mozilla one I don't see
how they are doing it also. As we have set that
Em 28/04/2007, às 09:47, Florian Schulze escreveu:
This is the biggest and hardest problem about js parsing. The spec
does
define how to handle it, I'm not sure now how the grammar reflects
that
though. Looking at C doesn't help, because there it always needs to be
present and can't be
Laura Creighton wrote:
In a message of Sat, 28 Apr 2007 18:22:50 +0200, Carl Friedrich Bolz
writes:
would be valid. This opens its own set of problems such as:
a = b
++ c
Which would most likely be parsed to be equivalent to:
a = b++;
c;
Whereas with the
Hi Armin!
Armin Rigo wrote:
On Sat, Apr 28, 2007 at 07:56:11PM +0200, Carl Friedrich Bolz wrote:
If another placeof pypy still uses os.open I am strongly
for fixing that.
There is the app-level os.open(), which of course uses the interp-level
os.open(). It means that if a backend only
Armin Rigo wrote:
Hi Carl,
On Sat, Apr 28, 2007 at 07:56:11PM +0200, Carl Friedrich Bolz wrote:
If another placeof pypy still uses os.open I am strongly
for fixing that.
There is the app-level os.open(), which of course uses the interp-level
os.open(). It means that if a backend
