Arihiro Yoshida
Arihiro Yoshida
Thanks as always. Your PEG optimizing method is very impressive. However, I decided to pass on introducing it now, because I could fixed the performance issue #47 with wholly satisfying...
> I can prepare the code and send a PR if you're interested. Of course, I'm interested in it. It would be very helpful.
Let me rewrite your expressions more precisely. The rule definition way you want: `expression
Thank you for your advice. I replaced every double underscore __ with a single underscore if it is in an identifier that consists of uppercase letters and underscores. Please check...
> How do you think about to rename also functions? I don't want to rename them anymore. I determined the function naming convention like 'class name'__'method name' to distinguish it...
Just for C. You can use it with a C++ compiler, but I don't support such usage.
Just because @elfring wanted to use PackCC with C++, I think. I accepted a part of @elfring's suggestion since I thought it had better comply with C++ standard as much...
@elfring, @MaxBarraclough, I'm going to close this issue because of the following reasons: - PackCC generates a C source code in a `.c` file (not in a file with the...
> I became curious if interests could grow further for involved standard compliance aspects. It might be just your impression, and isn't persuasive. > Some development concerns can be tackled...
It might be good to use `PCC_MALLOC()` also for the AST node allocator _by default_, and to enable users to introduce some independent allocator for it _optionally_. That is: ~~~c...