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.
