You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
Interesting! I never considered the possibility of wrapping the library to help decoupling. Thanks for your input!maple_shaft– maple_shaft ♦2013-02-22 13:55:13 +00:00Commented Feb 22, 2013 at 13:55
-
Wrappers are a good idea if you use them from square one. If you're already using the library directly, switching to a generic wrapper will require refactoring and re-testing a lot of code.Blrfl– Blrfl2013-02-22 14:02:22 +00:00Commented Feb 22, 2013 at 14:02
-
1@Blrfl yes, that's why it's not a step to be taken lightly. But in at least one case we had a 3rd party (OSS) library change all its packages and classnames between 2 minor releases, and had no recourse but to adopt it, so the refactoring had to be done anyway. This way, we ended up future proof as well as having the issue fixed that caused the requirement to use the new version.jwenting– jwenting2013-02-22 14:50:28 +00:00Commented Feb 22, 2013 at 14:50
-
@jwenting: Absolutely agree. I do the same thing with Boost because while some of their implementations are good, the interfaces can be obtuse. That, and they tend to change things around frequently, too.Blrfl– Blrfl2013-02-22 15:26:44 +00:00Commented Feb 22, 2013 at 15:26
-
3Note that some Linux distributions effectively maintain their own „forks” of software by backporting security patches to earlier releases.liori– liori2013-02-22 16:38:31 +00:00Commented Feb 22, 2013 at 16:38
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you