ebmDevMag.com home
ebm Developer's Magazine

developer's mag
main page

part 1
part 2
part 3
part 4
part 5
part 6

1 - File I/O on the eBookMan

    (download tutorial source .zip file)
    (download tutorial program .seb file only)

If you've programmed today's operating systems, communicating with a disk drive is just about the only way to create anything of permanence. The ebm changes that perspective, and gives programmers a simpler way to access permanent file storage.

ebm file organization can be somewhat odd compared to the 'hard drive' world. Most notably, files don't need to move; the file exists in the same memory as the program, and there is no concept (or need) to read in a file. Instead, the file is simply made accessible to the program (called mapping). Once you've mapped in a file, you can access it via a pointer in your code, and do anything you would to any other segment of memory, such as a structure or array. As you can imagine, a tremendous amount of time is saved, since nothing is loaded or copied.

Next Section

Copyright © 2001-2006 ebmDevMag.com - Legal Notice