[Vm-dev] The code in the src folders in the repository

[Eliot Miranda]

Hi Fabio, Hi All,

> On Jun 22, 2016, at 12:51 AM, Fabio Niephaus <lists at fniephaus.com> wrote:
> 
> AFAIK the pharo-vm projects generates the sources from the VMMaker package during a build.
> Wouldn't it be better if the OpenSmalltalk vm does the same? Then no one needs to generate source manually anymore and we don't have millions of lines [2] of generated code in the repository.

In short, we think nothing of burning pets cycles every time we make any change in the repository, kicking off many many builds.  We should think nothing of these few tens of megabytes of disc that keep a necessary record of the production VM source.  Reducing disc size here is a) optimising the wrong thing and b) optimising something quite cheap.  Both are cardinal errors.

> Fabio
> 
> [1] https://github.com/pharo-project/pharo-vm
> [2] see Eliot's stats at https://github.com/OpenSmalltalk/vm/graphs/contributors
> 
> -- 
> 
>> On Wed, Jun 22, 2016 at 4:02 AM David T. Lewis <lewis at mail.msen.com> wrote:
>> 
>> On Tue, Jun 21, 2016 at 11:11:28AM -0300, Laura Perez Cerrato wrote:
>> >
>> > Hi everyone,
>> >
>> > Excuse me if this has been asked already or it's documented somewhere and I
>> > missed it, but what's the criteria to update the code in /src, /stacksrc,
>> > /spursrc and other similar folders in the repository?
>> >
>> > -Laura Perez Cerrato
>> 
>> Good question. Traditionally, Eliot generates these sources periodically and
>> commits them to the repository (and in recent years I have done that chore for
>> the old trunk interpreter VM). At this point, unless Eliot advises otherwise,
>> I would suggest that no one other than Eliot should commit to the /src trees.
>> 
>> Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20160622/0fe40965/attachment.htm