On 09/04/2012 10:21 PM, Will Coleda wrote: > We were just noting how quiet #ps is, so I thought I'd throw this > question out to the list. > > What should we do with ext/nqp? > > 1) delete it, and update all our tools that use it to use winxed instead. > 2) replace it with the new nqp. > 3) leave it alone. > * ?
> I'm leaning towards #1 - if winxed is the defacto "HLL" in our build > process, I'd rather stick with a single language to fit that role, > rather than have 2 different options. Even if we keep #2, I'd > recommend rewriting any of our build steps to use winxed instead of > updating them to the new nqp syntax. Does winxed have a grammar engine or anything comparable that helps with parsing? The current NQP code heavily relies on NQP's implementation of Perl 6 grammars. Cheers, Moritz _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
