Re: Handling Structured Memory
Chris wrote;
> Maybe soon, the author will release his wrapper set, or maybe he has
> already.. I'll find out..
I just uploaded all my api libs to my website at the url:
http://pages.prodigy.net/mirwalds/win32.zip .
For a link to the bookmark on the page, use:
http://pages.prodigy.net/mirwalds/#win32 .
I included two folders in the zip, that you should be able to drop in your
include folder, and use include names such as " include winapi/user32.ew ".
The kernel32.ew file is just a set of routines and constants that I
frequently use, or had wrapped in the past. I never completely converted it
because of all the thread/process/memory stuff that we really don't need.
All the others are designed for Win9x, IE V5.01. They are useable on XP and
2000, but lack the additional goodies that the newer platforms offer. The
structs.e file that Chris was referring to is included in the dev folder.
There are many structures in there that haven't been converted yet, but the
definitions that appears in the respective header is commented for each. I
have found that it's better to define them when I'm actually using them, due
to differances in alignment between C and Euphoria.
You are welcome to include it in the archives Robert. I also fixed the
annoying set_packet_size() thing in tcp.ew, so that if a user doesn't
specifically call it, it'll set packets to 1024 bytes automatically. Calling
set_packet_size() overrides this default regardless of when it's called.
<2-cents>
I spent ALOT of time trying to keep track of prefixes before I saw Chris'
ideas for structs.e. There's just such an overwhelming number of duplicated
names in these api libs, it was a constant battle (heh) to try and remember
them all, and look them up when my memory failed me. The ability to re-use
the names was a god-send for these libs. I can sure live with strings to be
able to copy/paste the structure names from the docs into my code (some are
pretty long).
</2-cents>
Jason
|
Not Categorized, Please Help
|
|
