> Hi,
> 
> I have currently to issues:
> 
> 1] The stdout should be opend in binary-mode not text-mode.
> I run into problems as I tried to send an image to the webserver via 
> stdout on the windows platform. The problem seems to be that the stdout 
> (and might stdin) is opened in text-mode which makes all datastreams 
> altered.
>  From a few other mailing lists, the problem seems to be that the 
> default option on ANSI-C is the textmode for the standart-streams which 
> converts the line-carriges on windows.
> However, I didn't done anyting a long time in C, therefore I guess it's 
> more something for the next release.

Right now the stdout returned is the one that is opened by the terminal
by default. And it's always in text mode. There is two possibilities I see :

a) changing the output mode of stdout : I found the "setmode" C function
but it's neither ANSI nor POSIX, and I'm not sure it's supported on a
lot of platforms

b) closing then reopening the stdout. I remember using this trick by in
my system programming days, I don't remember exactly how it works and if
it's possible to do completely with current Neko API. Try to have a look
 and tell me if you need something.

> 2] I'm playing with haxe and neko and would like to build a few 
> standart-libaries (zlib, jpeg, etc.). What might would do my job much 
> easier, would be if there is anyhow a way to implement the native 
> c-datatypes, since I sometimes need to work with the unsigned versions 
> eg. of int32.

signed or unsigned is not so much a problem, since the representation is
the same, unless you want to do comparisons (greater or lower than). As
you know, Neko integers are 31-bit signed. If you need the whole
32-bits, for CRC for example, you can use the int32 std api (documented
here : http://nekovm.org/doc/view/int32

Best,
Nicolas



-- 
Neko : One VM to run them all
(http://nekovm.org)

Reply via email to