[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Thursday 06 January 2005 00:02, Elias Pschernig wrote:
> Well, for me, looks good enough for 4.2.
Cool. Shall we aim for next weekend (say, sunday 16th) for the feature
freeze?
> I think the only open issue was
> the missing "open" entry in the vtable.. and personally I couldn't find
> a proper solution, so Peter's solution of just leaving it out should
> work. We might actually add the memory files vtable from the example, so
> there would be 2 standard vtables: the libc file functions wrapper, and
> the memory files. Else we require everyone who wants memory files to
> copy/paste that code..
Yes, I agree.
I didn't look at the implementation too closely. How would one open a
memory file?
Using something like
pack_fopen_vtable(memory_vtable, ptr);
?
I'd still prefer something that looks (to the user) something like
pack_fopen_ex(PF_MEMORY, ptr);
just to hide the term `vtable' from user space.
Evert