It is beneficial to have an option in the Save statement in such a way that FORM can gzip-compress expressions in save files. See also the discussion at #433.
A possible way for the syntax is:
Save gzip savefile;
Save gzip savefile expressions...;
Here gzip is a contextual keyword. The disadvantage of this syntax is that the user cannot specify gzip as the save filename (but normally nobody would want to do that).
If the save file format has room to record whether expressions in the file are gzip-compressed or not (or with other compression formats), then the syntax of the Load statement does not need to be changed; the user can just use Load as in the past and it transparently loads expressions if compressed.
It is beneficial to have an option in the
Savestatement in such a way that FORM can gzip-compress expressions in save files. See also the discussion at #433.A possible way for the syntax is:
Here
gzipis a contextual keyword. The disadvantage of this syntax is that the user cannot specifygzipas the save filename (but normally nobody would want to do that).If the save file format has room to record whether expressions in the file are gzip-compressed or not (or with other compression formats), then the syntax of the
Loadstatement does not need to be changed; the user can just useLoadas in the past and it transparently loads expressions if compressed.