API/ABI break: associate behaviour flags with client object instead of for each function call #105

Closed
opened 2017-01-14 05:09:57 +00:00 by ariadne · 2 comments

This makes things more consistent and allows for cleaner implementation of some things (like prefix relocation), but breaks ABI. Thusly it cannot go back to 1.1 series.

This makes things more consistent and allows for cleaner implementation of some things (like prefix relocation), but breaks ABI. Thusly it cannot go back to 1.1 series.
plicease commented 2017-01-14 14:40:18 +00:00 (Migrated from github.com)
Poster
Owner

I think this is the right approach. Also my Perl module already does this, so even it breaks my code it shouldn't break my interface.

I think this is the right approach. Also my Perl module already does this, so even it breaks my code it shouldn't break my interface.
Poster
Owner

And that is that.

And that is that.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ariadne/pkgconf#105
There is no content yet.