| Re: [AD] Custom packfiles #2 |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Custom packfiles #2
- From: Chris <chris.kcat@xxxxxxxxxx>
- Date: Mon, 03 Jan 2005 07:14:35 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Zlt8dg5d6WfhcjpN3PDBpF0i0XUoS16d58zG6oIefcwuGr77E8r6UCzUr69SuAT94dcMUPmQqy3ljJdMls98GqKHjRCnLjya3qEORRqrJ8nxrcTkDEn5i7vTkTzNoSKw/l8Dch8Uq9MjorVa41h8qjUDfgGoy/6Nw3emN3lfhSU=
Elias Pschernig wrote:
Heh. I guess, it really can be left to addons to provide proper open
functions, and therefore they need not be in the vtable.
I don't know. It just seems right to have an open function in the
vtable. I don't like the idea of pre-opening the file before sending it
to pack_fopen_vtable. Besides, all it is, is an extra 8 bytes. If the
open and close entries are NULL, just don't call them.. assume success.
One other thing I'm thinking is, maybe it would be a good time to split
file.c up? 3000+ lines just is too big for me. E.g. file.c, packfile.c
and lzss.c
Sounds like a good idea to me. Some of those source files are ungodly big.