Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
this was already possible, but now it's slightly safer
|
|
|
|
|
|
|
|
this will be needed for storing vfs_op's properly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this avoid accidental dereferences, and now it's easy to tell apart
which pointers are safe to directly read and which aren't.
cons:
- const is completely discarded
|
|
`()` means that any amt of arguments will be accepted, which isn't what
i want
|
|
|
|
|
|
|
|
|
|
|
|
it occureed if the path_simplify returned a negative value - instead of
being interpreter as an error it just carried on, ending up in an
infinite loop.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The length is a int, because the syscall will have a signed output. A
negative return value will mean an error (such as when it gets called
by a childless process).
|
|
|
|
|
|
most syscalls will have to do this to copy memory around or whatever.
it's pretty ugly too, but i can't come up with a better abstraction...
|
|
|