#93 amberc exports more than it imported

Open
opened 1 year ago by nero · 1 comments

Originally at 2011-11-02T09:04:19Z by Göran Krampe

In other words, code can "linger on" in the js files. amberc should only export what it just imported - or in other words, it should only produce js code based on the st filein.

Since it can not nuke the js code first (it may be recompiling Kernel or Compiler) then it has to keep "track" of what it filed in, and then make sure it exports the same classes/methods. This should also fix issue number 51 in fact.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally at 2011-11-02T09:04:19Z by Göran Krampe In other words, code can "linger on" in the js files. amberc should only export what it just imported - or in other words, it should only produce js code based on the st filein. Since it can not nuke the js code first (it may be recompiling Kernel or Compiler) then it has to keep "track" of what it filed in, and then make sure it exports the same classes/methods. This should also fix issue number 51 in fact. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/379169-amberc-exports-more-than-it-imported?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github). </bountysource-plugin>
Herby Vojčík commented 1 year ago
Owner

When recast from 'compiler' to 'scripted image builder and package exporter', this may be a non-issue...

When recast from 'compiler' to 'scripted image builder and package exporter', this may be a non-issue...
Sign in to join this conversation.
No Label
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.