In C, it could look like
Write(char *filename, void *data, uvlong number_of_bytes);
so I don't think it has an Open syscall, or probably you read
everything into memory, modify the memory, then write it back. 64-bit
systems can store quite a bit, but this philosophy will get old
almost immediately:
$ sed2c '1s/^/@/' # given sed2c is a program that converts sed
commands to C
char *buffer;
buffer = malloc(FileLen("f"));
Read("f", buffer, FileLen("f"));
b[0] = '@';
Write("f", buffer, strlen(buffer));
Does that seem like a bit much?
On Feb 10, 2008, at 1:01 PM, erik quanstrom wrote:
There's an OS (complete with a Window Manager, IDE, Web Browser, and
even some games) written entirely in assembly: http://
www.menuetos.net/
Everyone has 24 hours in a day, but some use it more than others ;)
i can see from their documentation, that i have been using my time
quite
a bit more effectively:
"Menuet has no roots within UNIX or the POSIX standards,
nor is it based on any particular operating system. The design
goal has been to remove the extra layers between different parts
of an OS, which normally complicate programming and create bugs.
here's their write system call:
rbx - 1 Write
rcx - Ignored
rdx - Bytes to save
rex - Pointer to data
rfx - Filename pointer
!?
- erik
