[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-apl] ⎕TZ should not be saved

From: Juergen Sauermann
Subject: Re: [Bug-apl] ⎕TZ should not be saved
Date: Sun, 13 Sep 2015 16:05:36 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0

Hi Blake,

yes, )DUMP sorts variables and functions by name, and dumps functions before variables.

/// Jürgen

On 09/12/2015 03:48 PM, Blake McBride wrote:
Hi Juergen,

I see your point, and it makes sense.  One caviet though, I don't know if this is the case or not but, I hope that when a )DUMP occurs the functions and variables are sorted.  )DUMP makes more sense to use in a SCCS.  If I change one function, I wouldn't want a different sort of the )DUMP file to make the SCCS think more changed.  Does )DUMP sort its output?



On Sat, Sep 12, 2015 at 4:55 AM, Juergen Sauermann <address@hidden> wrote:
Hi Blake,

yes, the discussion was to change ⎕TZ on )LOAD. The general strategy of GNU APL to save
as much information as possible because some information that looks like not being used today
may become relevant at a later point in time.

Removing ⎕TZ would not help with source control system, because there is another timestamp
in the workspace file that changes as well when the workspace is )DUMPed or )SAVEd. Also,
the order of objects in a workspace file may change when a workspace is )LOADed and then
)SAVEd again.

Therefore a source control system would detect a change in the file even if we would not store ⎕TZ.
And I believe that is good because the state of the workspace has in fact changed, even though the
variables or functions inside the workspace have not.

/// Jürgen

On 09/10/2015 04:48 AM, Blake McBride wrote:
Sorry.  I now remember this is a topic we covered before and a change was made so the )LOAD ignored ⎕TZ.  That works.

The thing that brought the problem up is because a garbage/unused ⎕TZ, although not loaded, is saved.  This creates problems with source code control systems because ⎕TZ may keep changing artificially when two developers are working on the same code but in different time zones.

Bottom line - ⎕TZ should not be saved.



On Wed, Sep 9, 2015 at 9:10 PM, Blake McBride <address@hidden> wrote:

⎕TZ should not be saved with SAVE or DUMP.  I should be able to count on ⎕TZ containing the locally applicable time zone - not the one the developer had!  If, for some reason the developer wants to change ⎕TZ, it should be done explicitly in a function.  A global value should never be saved.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]