Save {mvbutils} | R Documentation |
These function resemble save
and save.image
, except that any functions which have been mtrace
d (see the debug package) will be temporarily untraced during saving (though the debug package is not needed to run them). Save()
is like save.image()
Save.pos(i)
saves all objects from the i
th position on the search list in the corresponding .Rdata file. There is less flexibility in the arguments than for the system equivalents.
Save() Save.pos( pos, path, ascii=FALSE)
pos |
character or numeric position on search path |
path |
directory or file to save into (see DETAILS). |
ascii |
file type, as per save |
If a function f
is saved while mtrace
d and then restored into a different R session, there will be an error message when you try to run f
. Assuming that the debug package is loaded, this can be fixed by mtrace(f,FALSE)
or mtrace(f)
if you really want to debug f
. However, you can avoid the problem in the first place by always calling Save
and Save.pos
; this is faster than manually untracing and retracing, and avoids losing any breakpoints. If you use the cd
system in mvbutils
, you will rarely need to call Save.pos
directly; cd
, move
and FF
will do it for you.
To exclude objects from saving, store their names in options( dont.save)
. The default exclusion is .packageName
; good additions might be last.warning
and .Last.value
.
path
is normally inferred from the path
attribute of the pos
workspace. If no such attribute can be found (e.g. if the attached workspace was a list object), you will be prompted. If path
is a directory, the file will be called ".Rdata". If you specify path
, it must be a complete directory path or file path (i.e. it will not be interpreted relative to a path
attribute).
Mark Bravington
save
, save.image
, mtrace in package debug
## Not run: Save() # Save.pos( "package:mvbutils") # binary image of exported functions Save.pos( 3, path="temp.Rdata") # path appended to attr( search()[3], "path") ## End(Not run)