Welcome, Guest. Please login or register.

Author Topic: More about why SObjs: isn't a great idea  (Read 6328 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Fats

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 673
    • Show all replies
Re: More about why SObjs: isn't a great idea
« on: November 02, 2010, 11:28:45 PM »
Quote from: Matt_H;588526
And a static program is a product of the tools available at the time it was compiled.


This thus also means that if a security flaw in one of the libs that are linked to a lot of programs, they need to be relinked and redistributed to the user.
I know, mentioning security and Amiga in the same context does currently not make much sense.

greets,
Staf.
Trust me...                                              I know what I\'m doing
 

Offline Fats

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 673
    • Show all replies
Re: More about why SObjs: isn't a great idea
« Reply #1 on: November 04, 2010, 10:11:14 PM »
Quote from: Karlos;589109
That doesn't work. If you load application X which requires progdir:foo.library A and then start application Y which requires libs:foo.library B, application Y isn't going to work. The reason being that the request to open foo.library is going to note that it's already open and return the base pointer to it.


This is not something inherently connected to .library style libraries but to how the loading/caching is currently implemented in exec.

greets,
Staf.
Trust me...                                              I know what I\'m doing