[Corona-devel] Re: threads and allocation

[Chad A. <ae...@vr...>]

Hi Chris,

>>That sounds cool.  Got a web site for the project or anything?
> 
> 
> yes.
> 
> www.workspace-unlimited.org . There's nothing about this current
> project up yet, though.

Looks nice!

>>Hm, that could be possible...  OpenImage does do a few other allocations as 
>>well, however.  It allocates a File object first, then the various loading 
>>structures needed.  (The allocation for PNG, for example, is actually done by 
>>libpng.)  It seems to me that it would be difficult to modify these loaders to 
>>deal with one block of memory.
>>
>>What do you think about adding a new interface: corona::Allocator and allowing 
>>the user to specify a custom allocator?  One issue there would be: do we pass it 
>>in for every load/save function, or do we allow a global setting, or both?
>>
> 
> 
> I like the allocator idea; I imagine anybody wanting allocators
> would probably be the same reasons I have. In which case, per-load/save
> allocation is easier, allowing me easily to cycle through preallocated memory
> blocks. Again, the work depends if others are interested, should you consider
> it worth your while to go ahead with it. Don't do the work just on
> account of me!

Allocators as described above would be a really nice thing to have, but I simply 
don't have the cycles lately, as I'm sure you can tell by the latency of this 
response.  (The new semester hit, and hard.)  However, if anyone else has some 
free time and the desire to implement it, I'd gladly help with getting it 
checked in...

Thanks,
Chad