> The lseek, read, write system calls have served us well for decades > because they implemented a simple abstraction that a Unix/Linux file > can be seen from "any application" (ie, not just the one creating the file) > as a sequence of bytes. The idea of a hole as an "absence of data" that > should be supported by these system calls is a direct violation of that > principle.
Fully agreed. Philippe Bergheaud _______________________________________________ ast-users mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-users
