On Tue, Mar 25, 2014 at 1:50 PM, Jeff Hardy wrote:
> On Tue, Mar 25, 2014 at 10:23 AM, Pawel Jasinski
> wrote:
>> Here is my work in progress:
>> https://github.com/paweljasinski/ironpython3/compare/parser3
>> Comments are welcome.
>
> My initial thought is that it's way too big to be one commit.
On Tue, Mar 25, 2014 at 1:25 PM, Pawel Jasinski
wrote:
> agree, it was a first point where ipy stopped complaining on startup :-)
> I am sure git offers a reasonable help, so I can split things into
> digestible (testable) pieces.
`git reset` will "undo" the commit back into the working tree, and
On Tue, Mar 25, 2014 at 10:23 AM, Pawel Jasinski
wrote:
> Here is my work in progress:
> https://github.com/paweljasinski/ironpython3/compare/parser3
> Comments are welcome.
My initial thought is that it's way too big to be one commit. :) it's
too much to digest or review all at once.
I also mad
Here is my work in progress:
https://github.com/paweljasinski/ironpython3/compare/parser3
Comments are welcome.
On Tue, Mar 25, 2014 at 10:56 AM, Jeff Hardy wrote:
> On Mon, Mar 24, 2014 at 3:47 PM, Pawel Jasinski
> wrote:
>> hi,
>>
>> I started to tinker with parser. Does anybody else work on p
On Mon, Mar 24, 2014 at 3:47 PM, Pawel Jasinski
wrote:
> hi,
>
> I started to tinker with parser. Does anybody else work on parser already?
One thing to watch for is that parts of the parser are auto-generated
by some Python scripts (there are comments in the files that say which
script was used)
