Multiple Riders can be positioned at different locations in a file. A Rider cannot be positioned beyond the end of a file. R.eof indicates if the end of the file has been passed. Less bytes will be read when reading over the length of the file. Oberon uses the little-endian byte ordering for exchanging files between different Oberon platforms.
Files are separate entities from directory entries.
Files may be anonymous by having no name and not being registered in a directory. Files only become visible to other clients of the Files module by explicitly passing a File descriptor or by registering a file and then opening it from the other client. Deleting a file of which a file descriptor is still available, results in the file becoming anonymous. The deleted file may be re-registered at any time. A file might have more than one rider operating on it at different offsets in the file.