Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternate output file name for generated files #4

Closed
wants to merge 1 commit into from

Conversation

Jissai
Copy link
Contributor

@Jissai Jissai commented Mar 6, 2013

In grammar file directives @scanner, @parser, @ParserTree, @TextHighlighter
now accept the option FileName=<file_name>
Where <file_name> is the name of the file to be generated. <file_name>
must include the extension (ex .cs / .vb)

In grammar file directives @scanner @parser @ParserTree @TextHighlighter
now accept the option FileName=<file_name>
Where <file_name> is the name of the file to be generated. <file_name>
must include the extension (ex .cs / .vb)
@Jissai Jissai closed this Mar 6, 2013
@Jissai Jissai reopened this Mar 6, 2013
@Jissai
Copy link
Contributor Author

Jissai commented Mar 6, 2013

I made modification on sourcecode from codeproject v1.3 of tinyPG.
I see there are changes in GitHub but i don't know if they are more recent or not.
I will rework the code to start from github sources

@tomspilman
Copy link
Member

Hi Jissai.

First thanks for the contribution!

This is an "unofficial" fork of TinyPG (I also posted to your question on CodeProject). I created it because we had a need for some new features (mainly case insensitive symbols) and was frustrated by the author ignoring my questions.

I decided it would be best to have public fork of TinyPG on GitHub that we could improve and share with others.

I see there are changes in GitHub but i don't know if they are more recent or not.

We forked from the 1.3 sources originally some months ago:

https://github.com/SickheadGames/TinyPG/tree/7a4ad9681ba047d4bda03978580d081aa0f9454e

... but we've added new features to the code since then. Those are most likely the differences you are seeing.

@tomspilman
Copy link
Member

From looking thru this diff the differences you are seeing are from these fixes/features:

  • ParseError now properly initializes file and line number information.
  • Production rules without a code block will by default evaluate their sub-rules.
  • IDE now uses C# 3.x compiler when testing the generated parser code.
  • Support for [IgnoreCase] flag on terminal symbols.
  • New [FileAndLine] attribute for redefining the file and line number reported in errors.

This is all new code that didn't exist in 1.3.

@Jissai
Copy link
Contributor Author

Jissai commented Mar 6, 2013

Ok, I will port my modifications on the latest code, ignore this pull request, I will try to make another cleaner tomorrow. (not quite familliar with git)

Another planned modification is to make TinyPG usable from command line for production. I saw a modification on codeproject, and i have coded one. I will see which one is the best.

Happy to see there is still life on this project, because we plan to use it a lot.

@tomspilman
Copy link
Member

not quite familliar with git

Yea... I've been using it for a year and still don't feel fully comfortable with it, but it gets better.

make TinyPG usable from command line for production

I actually added an issue the other day to remind me to add that feature: #3

I'd be glad to see a pull request that adds a new command line project for it.

Happy to see there is still life on this project, because
we plan to use it a lot.

That is why we forked it.... we love it, are using it a lot, and want to see it improve.

@tomspilman tomspilman closed this Mar 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants