| 1 |
On 30/10/2012 13:39, Michael Mol wrote: |
| 2 |
> In general, I agree...but Boost wasn't intended to be a shared library, |
| 3 |
> so there shouldn't be a conflict there. |
| 4 |
|
| 5 |
But there are shared libraries, and they are not small either. And I'd |
| 6 |
rather, say, hunt an RWX section problem (a security problem) with a |
| 7 |
single shared library rather than having to hunt it down in a dozen or so. |
| 8 |
|
| 9 |
Besides, honestly it's not that bad. I think that half the headache that |
| 10 |
we're having is due to the slotting more than from boost itself. And the |
| 11 |
other half is due to people actually not going to fix their crap because |
| 12 |
"oh I can just use the older version" (until a new compiler or C library |
| 13 |
comes out). |
| 14 |
|
| 15 |
I've had to do my share of porting to newer boost — and as I said most |
| 16 |
of the headaches have been for the build system to find the object, |
| 17 |
rather than anything else. |
| 18 |
|
| 19 |
-- |
| 20 |
Diego Elio Pettenò — Flameeyes |
| 21 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
Archives