[Vm-dev] building plugins outside the tree

Eliot Miranda eliot.miranda at gmail.com
Tue Mar 20 18:20:33 UTC 2018

On Tue, Mar 20, 2018 at 11:10 AM, tim Rowledge <tim at rowledge.org> wrote:

> > On 20-03-2018, at 10:51 AM, Eliot Miranda <eliot.miranda at gmail.com>
> wrote:
> >
> > Over my dead body.  Look, the generated sources all start with comments
> that say
> >
> > /* Automatically generated by
> >
> > they could say
> >
> > /* Automatically generated by
> > .....
> >  */
> OR we could run the generated code through an obfuscator... wait, what am
> I saying, this is C code already. An important problem here is that I can
> pretty much guarantee nobody ever 'see's that comment, nor would take any
> notice of it if they did. Because code mokeys have all taken off their
> hoodies, handed over their beer/red bull/mountain dew/whatever and told
> their buddies "ok, watch *this* dude!"
> >
> > But going back to generating the VM sources every time one wants to
> build a VM, having, as Ben points out the possibility of changes in Slang,
> variability due to sets changing generated sources, date stamps changing,
> etc, etc.  NO!!!!!!!  I can't believe you're serious.
> Who needs to be serious? Fair point about the variability of details
> important to other tools though. I can't imagine we couldn't work around
> all that but as you say, who has the time?

That's not the point.  The point is that *unless* one versions the
generated source code that produced a specific VM, you could *never know
for certain* that the source you did generate later on was the same.  So
for reproducibility and general sanity the generated C is versioned.

best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20180320/01e5b5ee/attachment.html>

More information about the Vm-dev mailing list