Alex:
As you probably know, compilers in the old days were implemented in a
series of stages as separate processes due to memory size limitations.
The output from the previous stage was fed to the next stage as
compilation proceeded until object files were produced.
Maybe it makes sense for the compiler to output everything the publisher
needs (final ASTs and/or other metadata, etc) when it exits.
Then a separate publisher process could optionally use that output to do
all the expected publish-type things without being intermingled with the
compiler itself.
The publisher would probably be simpler to understand on its own and
maybe more people could be involved with it.
Jason
On 2/26/2018 8:49 PM, Alex Harui wrote:
The only
downside I've thought of is just that it is weird to have a publisher
attached to the compiler. I don't think most compilers have a publisher.
--
Jason Guild
Analyst/Programmer V
State of Alaska - Department of Transportation & Public Facilities
Information Systems and Services Division
820 E. 15th Ave.
Anchorage, Alaska 99501
