Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS_ENTRY ergonomics #940

Open
SiegeLord opened this Issue Oct 13, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@SiegeLord
Copy link
Member

SiegeLord commented Oct 13, 2018

See some discussion in #931.

Essentially, want Allegro to allocate FS_ENTRY less often (so the user has to destroy it less often), as well as provide more convenience overloads that just take the C string directory/file name.

@fatcerberus

This comment has been minimized.

Copy link
Contributor

fatcerberus commented Oct 13, 2018

Do we have al_dup_fs_entry() or similar? If not, perhaps we should as part of whatever concrete change comes from this. This way we could have whatever replaces al_read_directory just allocate a single structure in the beginning and if the user wants to keep a particular entry around (probably not a common use case), they can make a copy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.