Re: Including translations of Jison in GitHub
- Robert Plummer
- 2012-01-19 @ 20:39
I went ahead and made the changes on my github fork and have updates the
pull request. But just fyi, here is the link if you want to check it out:
It is working fantastic! I have 2 parsers (tiki and phraser) working
Lets push it!
On Thu, Jan 19, 2012 at 10:46 AM, Robert Plummer <
> So I propose in my github fork that we use the folders like this:
> In my case I have a jison.js & template.php files. The template.php file
> is the translation of the jison output of js in php and is injected with
> all the goodies from jison. Right now I distiguish languages in the .jison
> file in the following manner:
> - Lines that are followed by a "//js" artefact are stripped from the
> php output
> - Lines that start with a "//php " artefact are used in the php output
> with the artefact stripped from the beginning
> - Lines that have neither are left alone.
> I think this is a really great way of incorporating new ports of jison
> into the development world. I think ideally we'd use some sort of wrapper
> to distinguish 1 language form another (like /*php /php*/), but for the
> time being, this works great, and now we have unified languages, empowering
> ajax and the server if we don't have tools like node.js to throw around.
> What do you guys think?
> On Mon, Jan 16, 2012 at 8:08 AM, Robert Plummer <
> email@example.com> wrote:
>> Hey guys,
>> Just wondering where the best place to commit a php jison translation
>> will be in the GitHub repo. Let me know, thanks!
>> Robert Plummer
> Robert Plummer