OpenEuphoria

Upcoming changes in win32lib internals

• Posted by CChris <christian.cuvier at agriculture.gouv.fr> Jun 05, 2007
• 543 views

Hi all,

As the next version of win32lib will feature a much improved/enhanced
structure engine (among others), its internal organisation will change
somewhat. In particular, w32support.e will spin off the structure engine 
in a new file called w32memory.ew (which includes the still existing
w32support.e).

I would like to have an idea of how much code relying on the internal file
stucture of win32lib there is around.

It was pointed out to me that Unicode.ew, an utility file for EuCOM, would be
affected. Fortunately, it actually doesn't need the routines in w32support.e 
and could use the standard allocate() and free(), unless I am missing 
something about memory allocations.

My question is: is there a need to spin off from w32memory.ew a basic memory
allocation engine which could be used standalone (and which would be enough
for Unicode.ew)? Assuming this is feasible, which I doubt given the current 
unforgiving global symbol resolution rules in Eu. The other option is to 
merge back two 3,000 line files together as w32support.e.

Note: currently, there are no plans to shuffle the contents of series.e, 
options.e or seqops.e around.

Thanks in advance for the feedback.

CChris