Jeremy Hylton wrote:
> I would like to keep them separate. The compiler produces code
> objects, but consumers of code objects don't need to know anything
> about the compiler.
Please do keep these separate - the only reason I've ever had to muck with
code objects is to check if a function is a generator or not, and including
the entire compiler header just for that seemed like overkill.
It's not a huge issue for me, but the separate header files do give better
'separation of concerns'.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.blogspot.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4