Hi All,

Just FYI, I've pushed up the feature/parser3 branch to github.  So far
I've just made changes to the csound_orc.y and csound_orc.l, following
the design of the parser3 test project.  As it is, I'm getting less
shift/reduce errors as the current parser in develop, which I consider
a good sign.

As it is, the branch does not currently compile.  I did some work to
start updating code towards that end but it is not quite done.  I'll
be working towards getting things compiling first, then work to
rewrite the other parts of the compiler to work with the new tree
structure being produced (as well as the moving of the symbol table
additions to the semantic analysis phase).  I'm also planning to
finally move the parallel analysis stuff out from the parser and into
it's own compiler phase.

I suspect with my upcoming schedule (September is quite busy), it will
take two to three weeks to get a working version going. While things
look good, there's still quite a bit I don't know if it'll work until
I get to a point where I can view the generated TREE structure.
That's just to say that it's not a definite yet whether this branch
will work. :)  I'll update here when there's something to test.

Thanks!
steven

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It might take you only 2 to 3 weeks, but I think the rest of us mere
mortals would need months or years for this kind of work ;)

On 25 August 2014 19:59, Steven Yi  wrote:
> Hi All,
>
> Just FYI, I've pushed up the feature/parser3 branch to github.  So far
> I've just made changes to the csound_orc.y and csound_orc.l, following
> the design of the parser3 test project.  As it is, I'm getting less
> shift/reduce errors as the current parser in develop, which I consider
> a good sign.
>
> As it is, the branch does not currently compile.  I did some work to
> start updating code towards that end but it is not quite done.  I'll
> be working towards getting things compiling first, then work to
> rewrite the other parts of the compiler to work with the new tree
> structure being produced (as well as the moving of the symbol table
> additions to the semantic analysis phase).  I'm also planning to
> finally move the parallel analysis stuff out from the parser and into
> it's own compiler phase.
>
> I suspect with my upcoming schedule (September is quite busy), it will
> take two to three weeks to get a working version going. While things
> look good, there's still quite a bit I don't know if it'll work until
> I get to a point where I can view the generated TREE structure.
> That's just to say that it's not a definite yet whether this branch
> will work. :)  I'll update here when there's something to test.
>
> Thanks!
> steven
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well, I did spend a lot of time on the current parser, so I'm
rewriting code I mostly know already.  That certainly helps!  (I'm
sure it'd be pretty slow going if I tried to modify Cabbage. :P)

On Mon, Aug 25, 2014 at 2:09 PM, Rory Walsh  wrote:
> It might take you only 2 to 3 weeks, but I think the rest of us mere
> mortals would need months or years for this kind of work ;)
>
> On 25 August 2014 19:59, Steven Yi  wrote:
>> Hi All,
>>
>> Just FYI, I've pushed up the feature/parser3 branch to github.  So far
>> I've just made changes to the csound_orc.y and csound_orc.l, following
>> the design of the parser3 test project.  As it is, I'm getting less
>> shift/reduce errors as the current parser in develop, which I consider
>> a good sign.
>>
>> As it is, the branch does not currently compile.  I did some work to
>> start updating code towards that end but it is not quite done.  I'll
>> be working towards getting things compiling first, then work to
>> rewrite the other parts of the compiler to work with the new tree
>> structure being produced (as well as the moving of the symbol table
>> additions to the semantic analysis phase).  I'm also planning to
>> finally move the parallel analysis stuff out from the parser and into
>> it's own compiler phase.
>>
>> I suspect with my upcoming schedule (September is quite busy), it will
>> take two to three weeks to get a working version going. While things
>> look good, there's still quite a bit I don't know if it'll work until
>> I get to a point where I can view the generated TREE structure.
>> That's just to say that it's not a definite yet whether this branch
>> will work. :)  I'll update here when there's something to test.
>>
>> Thanks!
>> steven
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> rewriting code I mostly know already.  That certainly helps!  (I'm
> sure it'd be pretty slow going if I tried to modify Cabbage. :P)

Not just Cabbage. Modifying any vegetable is a slow and time consuming
process :)

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

=)

so it sounds like both of you are in the right place, which is good for 
both, you and us.

so please continue, and in case you need a chicken (rory) or a beer 
(steven) as supplement for your food, we will try to make this possible.

(no rory, the beer is really for steven. cabbage needs some meat.)

	j



Am 25.08.2014 um 20:17 schrieb Rory Walsh:
>> rewriting code I mostly know already.  That certainly helps!  (I'm
>> sure it'd be pretty slow going if I tried to modify Cabbage. :P)
>
> Not just Cabbage. Modifying any vegetable is a slow and time consuming
> process :)
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I’ve modified cabbage last week. Made a soup.
========================
Dr Victor Lazzarini
Senior Lecturer
NUI Maynooth, Ireland
victor dot lazzarini at nuim dot ie




On 25 Aug 2014, at 19:17, Rory Walsh  wrote:

>> rewriting code I mostly know already.  That certainly helps!  (I'm
>> sure it'd be pretty slow going if I tried to modify Cabbage. :P)
> 
> Not just Cabbage. Modifying any vegetable is a slow and time consuming
> process :)
> 
> ------------------------------------------------------------------------------
> Slashdot TV.  
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I tried forking it on github with mixed results.

On 26 August 2014 01:27, Victor Lazzarini  wrote:
> I’ve modified cabbage last week. Made a soup.
> ========================
> Dr Victor Lazzarini
> Senior Lecturer
> NUI Maynooth, Ireland
> victor dot lazzarini at nuim dot ie
>
>
>
>
> On 25 Aug 2014, at 19:17, Rory Walsh  wrote:
>
>>> rewriting code I mostly know already.  That certainly helps!  (I'm
>>> sure it'd be pretty slow going if I tried to modify Cabbage. :P)
>>
>> Not just Cabbage. Modifying any vegetable is a slow and time consuming
>> process :)
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/