How to make changes to the parser?

[zenspider]

It looks like it isn't actually possible because it is compiled into the stone? I can't tell.

[AllenOtis]

Ryan,

Yes, you would need access to both the public sources under
git and the smalltalk vm source tree (currently being worked on
by HPI under NDA).

For performance the parser is calling
object manager functions directly, rather than calling
in through the public GCI interface. If object manager functions
were exported from libgcilnk the parser could possibly be a separate
shared library, but you would not want arbitrary C extensions to
ever call the object manager directly ...

Parser work flow is
build the byacc tool (has only been tested on Linux)

edit parser files as needed to make changes

run the yacc.sh script . This copies generated files into
the src directory from which libgclink shared library is built

rebuild the libgcilnk shared library , thus recompiling
the parser primitives which are in this library.

Allen

[zenspider]

(waves at Allen)

Suck. :/

So... I guess I can submit untested pull requests... or I can request an NDA?

[timfel]

We have some 1.9 parser changes in our repository - we'll have to talk to @pbm to upload builds of that.

[zenspider]

Can this be documented now?

[AllenOtis]

Issue #234 is obsolete and should be closed.
See issue #352 for the current state of the parser .

On Fri, Mar 13, 2015 at 2:45 PM, Ryan Davis [email protected]
wrote:

Assigned #234 #234 to @AllenOtis
https://github.com/AllenOtis.

—
Reply to this email directly or view it on GitHub
#234 (comment).

[zenspider]

closing