On Mon, 2014-06-16 at 10:32 -0700, David B. Lamkins wrote: > There does not seem to be a case in which fixing a function results in a > timestamp other than 0 0 0 0 0 0 0 as a result of 2⎕AT. However, saving > a workspace via )OUT does result in *some* functions having a reasonable > timestamp while others have their timestamp set to the Linux Epoch (1970 > 1 1 0 0 0 0). > > I believe there are two issues: > > 1) Fixing a function in APL should set the function's timestamp; 2⎕AT > should return the timestamp and not 0 0 0 0 0 0 0. > > 2) )OUT should write the same timestamps that 2⎕AT returns. > >
Added: 3) .xml workspaces should include a function's timestamp as an attribute. )LOAD should restore the timestamp.
