Arihiro Yoshida
Arihiro Yoshida
@ccleve , @ethindp , I have introduced the import functionality. Please check it. > **`%import` `"`_import file name_`"`** > > The content of the specified import file is expanded at...
Thank you for your immediate feedback!
Thank you for the helpful information! I do remember the request you have likely with a passion, but sorry, I still can't do it because of many things I have...
Hello @dolik-rce , Regarding this PR, can PackCC rely on your project [pegof](https://github.com/dolik-rce/pegof) for PEG optimization? I keep the role of PackCC as a tool that just generates a parser...
@andrewchambers , I have fixed this issue. I inform you, just in case.
@awrc , thank you for the helpful comment! @0alfa , please use the syntax above. I'd like to close this issue as "not planned".
This issue can be caused by too long a value in the environment variable `PATH`. In my case, it was resolved by removing unnecessary entries from `PATH`.
The example [TinyC](https://github.com/arithy/packcc/tree/master/examples/ast-tinyc) might be helpful to find the solution for precise counting rows and columns. It uses the customized macro [`PCC_GETCHAR()`](https://github.com/arithy/packcc/blob/80b948595b2079bbc389366a890eaf39588bcace/examples/ast-tinyc/parser.peg#L26) with the text reader function [`system__read_source_file()`](https://github.com/arithy/packcc/blob/80b948595b2079bbc389366a890eaf39588bcace/examples/ast-tinyc/system.c#L136). In this...
Thank you for your suggestion with the interesting code. However, let me close this PR for the following reasons. * I want to stick to keeping PackCC with a single...
I have realized the similar thing you suggested, by using the _import_ feature. Please see [here](https://github.com/arithy/packcc/?tab=readme-ov-file#simple-ast-builder). It is actually less easier than your suggestion but has much more versatility.