| Re: [AD] Clarifying and revising filesystem API |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Coordination of admins/developers of the game programming library Allegro" <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] Clarifying and revising filesystem API
- From: Peter Wang <novalazy@xxxxxxxxxx>
- Date: Thu, 16 Apr 2009 10:47:58 +1000
2009/4/16 Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>:
>>
>> % File system hooks
>>
>> # File system types
>>
>> ## API: ALLEGRO_FILE_HANDLE
>
> No. Its not a file. Its an entry. This will just confuse people. Its generic
> for a reason.
That's why I refrained from ALLEGRO_FILE, but apparently the extra
"handle" isn't enough. I don't mind ALLEGRO_FS_ENTRY too much
(it's unfortunate that "filesystem" is so long).
But _these_ unqualified names really bother me:
al_get_entry_size, etc.
al_is_present, etc.
They could be dealing with absolutely anything.
Could you live with:
al_get_fs_entry_size, etc.
al_fs_entry_is_present, etc.
Replies for the rest later.
Peter