I will soon add the new sys.io package, which will be including
[neko|cpp|php].io packages :
*.io.File
*.io.FileInput
*.io.FileOutput
*.io.Process
*.FileSystem (will become sys.io.FileSystem)
As well as neko.Sys (and php.Sys and cpp.Sys) which will become sys.Lib.
Any change that you would like to see in the new API ?
Best,
Nicolas
I found myself trying to unzip (or untar?) files in memory, when it
wouldn't work unless I wrote it to the filesystem first.
It would also be great if we could add some little things like chmod to
the official API
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
You can do that already by using haxe.io.BytesOutput/Input.
> It would also be great if we could add some little things like chmod to
> the official API
Added here http://code.google.com/p/haxe/issues/detail?id=590
Best,
Nicolas
Thank you!
On Fri, 02 Dec 2011 14:49:29 -0800, Nicolas Cannasse
<ncan...@motion-twin.com> wrote:
> Le 02/12/2011 23:40, Joshua Granick a écrit :
>> It would be great to be able to simulate a file input or output using
>> bytes.
>
> You can do that already by using haxe.io.BytesOutput/Input.
>
>> It would also be great if we could add some little things like chmod to
>> the official API
>
> Added here http://code.google.com/p/haxe/issues/detail?id=590
>
> Best,
> Nicolas
Yes, both will coexist, at least on SVN until 3.0 is released (or 2.09
is we have time for an intermediate release).
Best,
Nicolas
Good move, bad class name.
import neko.Lib;
import sys.Lib;
I would suggest sys.Sys or sys.Env if nothing better comes up.
Is the new structure going to swap transparently to the right target?
IE: the current API has cpp.io.*, neko.io.*, etc, are these now going
to be into one single API? io.File + conditional compilation?
Also, it would be really handy if io.FileStat would return whether a
file/folder is hidden. The current implementation on XAPI is based on
the the item name in *nix ("." as the first char) and some very dodgy
call to the attrib command on Windows.
Having something more consistent would be ACE.
Last, would you consider moving anything to do with folders out of the
File class? Basically so you have similar File and Folder objects with
similar methods (read, create, remove)? I wrote about it here:
http://blog.zarate.tv/2010/06/19/a-folder-is-not-a-file/
(Sorry for the lack of formatting, got hacked not long ago!).
Cheers!
J
--
Juan Delgado - Zárate
http://zarate.tv
http://blog.zarate.tv