Re: nio development in Jawin

Hi,
you should not use malloc as this hogs JVM memory (local heap). It may rise
"Out of memory" exception in JVM. You can use SysAllocStringByteLen,
SysAllocString, CoTaskMemAlloc, Virtual Memory, etc. Forget malloc, alloca,
calloc, etc. Use them only if you should pass a local heap (or stack)
pointer to some function.



----- Original Message -----
From: "Roger I Martin PhD" <[email protected]>
Newsgroups: gmane.comp.windows.devel.jawin
Sent: Monday, May 16, 2005 5:47 PM
Subject: nio development in Jawin


> Hi.
>
> Morten, you are a fantastic project organizer!  Things look well
> maintained and things work.  I just upgraded my Platform SDK and the Ant
> script is nice.
>
> How should we develop/maitain the nio version?  Java version? support
> jdk 1.3 until the nio version reaches and passes in functionality? On
> the Java side the nio version can use the current as base classes and we
> set the ant compile to 1.3 or 1.4>.  On the cpp side I'm not certain.
> Compile flags?  Gets ugly especially if the nio bores down thru
>
http://cvs.sourceforge.net/viewcvs.py/jawinproject/jawin/cpp/jawin/StreamOnMemory.h?view=markup
> for example.
>
> One thing it will give us is speed and less work to do about byte endian.
>
> I'm also starting to have some success with the jawt on another project
> and am looking to use it in Jawin.
>
> Resizing a buffer may be problematic.
>
http://java.sun.com/j2se/1.5.0/docs/guide/jni/spec/functions.html#nio_support
> I'm experimenting...
>
> Any other areas of interest to anyone?
>
> -Roger
>