Interfacing
Persistant Persistent mass storage is handled by the eprom EPROM file area. It is interfaced by the :EPR device (OZ 4.7 and newerabove). This device follows the DOR conventions with the major type DM_Epr ($84). Internal eprom EPROM file area is accessed with :EPR.0 device name. :EPR.1, :EPR.2, :EPR.3 refer to eprom the EPROM file area in slot 1, 2 or 3 if when a formatted eprom EPROM or flash eprom card is available. Accessing the file requires opening with GN_Opf, followed by i/o operations (OS_Gb, OS_Pb, OS_Frm, OS_Fwm, OS_Mv...) and ended by closure is closed with GN_Cl. All usual read and write operations are performed just like standard RAM files, thanks to the temporary ram files stored in :RAM.-. This functionality is transparent for to the end user, the temporary files are deleted after closure of closing the file.
Saving a file to the eprom EPROM file area implies a full rewrite of writes the complete file , the again. The previous copy (if existingit still exist) is marked as deleted. EPR device can be used as default device in the Panel, keeping . If this mode is chosen, keep in mind that the available free space can quickly be wasted by the deleted files generated.
Wildcards
Wildcards have has been implemented for eprom filename manipulationon EPROM filenames. Supported wildcards are '*' and '?'. Thus :EPR.* or :EPR.? browses all available file areas. Filenames are automatically expanded in GN_Opf filename buffer. This feature is useful in applications like Pipedream. After loading a file with using wildcards, its the filename is expanded without wildcards in when using <>FC or <>FS filename displaying the first file it finds.