I also just had a thought: the new
fsspell was supposed to be for filesystems, but it so far seems to only be manipulating files. Question: should we change this to the
Python's modules related to file manipulation is a little bit messy. They've introduced more modules and kept the old modules along the way for the sake of backward compatibility. Since even the core modules requires separate installation procedure in Chaos, if we split the modules then it might become a little bit inconvenient to use them. I would go with a relatively big module that covers everything related to filesystem.
fs is a good name for such a module I think.
osmodule to retrieve operating system's kernel name/version and distro name/version etc. We can have modules like
macosto provide OS-specific functionality if it's really needed.
fsAPI currently supports:
copy(), and soon-to-be
rename(), all related to files.
rename() function is able to do more than just file renaming like changing the path then I think
move() name is more suitable.
str file_pointer = fs.open(some_path)but it would be a bad approach.
byteto the language and it will be prefixed with an integer like
2 byteetc. So that we can have the file pointer like
1 byte file_pointer = fs.open(some_path).
DTjust like how it's in Assembly. But I think
1 byteis cooler.
ast.cand use them in
interpreter.cfor the AST node types that you've introduced.
compiler.cfor the AST node types that you've introduced.
Chaos.cto provide an API to Chaos C extensions for the new data type.
2 bytesyntax to see how possible it's.
the bitwise operators are also valid for integers in C