Le 27/05/2016 19:51, Orchid Win7 v1 a écrit :
> On 26/05/2016 08:28 PM, Le_Forgeron wrote:
>> Le 26/05/2016 20:11, Orchid Win7 v1 a écrit :
>>> I also enjoy how if you try to link an executable, it whines about unresolved
symbols, but if you link an SO file, it's NOT considered an error to have missed half
of the necessary object files... (!)
>>
>> Shared lib (.so) are allowed to be completed later by other libs, or even the
loading binary.
> 
> Presumably this requires the executable to load everything in exactly the right
order though?

One ring to rules them all.

Do not make a lib per folder, make a single lib.

Just like your meal ends up in your stomach, it will nourish you.
Later you can learn cooking and try to have separate plates, including a sweet
dessert, if the code allows such split.
But sometime code is just a spaghetti meal and nothing else.

> 
>> It's at runtime that you will get your problems.
> 
> Indeed. This is what I feared... So at some point, when the program is running, it
will suddenly segfault for no apparent reason, and it will be mathematically
impossible to ever determine why. Great.

No, symbol resolution is done at the start of the program (unless you start using
black magic for delayed resolution... you can even load a shared library later, to
resolve a symbol that came from processing some text data... but it's not for the
light hearted and is
often not portable).

Post a reply to this message