Comment 2 for bug 1436315
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
The current condition is the result of a trade-off between inelegance of having these (and the other "MIR_CLIENT_DETAIL" functions) exported from libmirclient vs the cost of introducing another libmirclientdetail (say) library to contain everything that isn't just supporting the client API.
Suggesting making them C functions like the client API ignores the principle that not part of the client API.
As we get more and more "MIR_CLIENT_DETAIL" functions the argument for another library gets stronger.