Hisham Muhammad
Hisham Muhammad
> And for files that can be opened using the io.read can be done by making another file (in the destination directory) and copying over the contents. Yes, this is...
@jaromil Feel free to simplify the internals if it aids with the bugfix and preserves portability!
Agree that the name is unfortunate, but the lfs API has been there for a long time, it would break lots of stuff if it was changed. What's being proposed...
I agree the name is a bit odd and I wouldn't have chosen it myself, but IMO I don't think the change is worth the hassle: people would write code...
I think it should throw an error if the path does not exist; at least this is what I would expect to happen in any filesystem library. Returning an empty...
What do you mean by fail? Returning an exit code other than zero?
@ignacio Oh wow. If we're bumping lfs to 2.0, then we better take the opportunity to make any other API tweaks all at once :)
@Tieske `filecopy` as in copy file A to file B? can't it be done in pure Lua opening file A for reading and file B for writing and performing reads...
Was this ever addressed? I just bumped into a similar issue.
couldn't one just use `lua_newuserdata` instead of `malloc` to allocate the memory that's temporarily needed there and just leave it to the Lua GC to collect it?