[WASTE-list] WASTE 3.0d4 Evaluation Kit now available

Marco Piovanelli marco.piovanelli at pobox.com
Wed Nov 2 09:37:02 EST 2005


On Tue, 1 Nov 2005 22:14:43 -0500,
Alfred Van Hoek (vanhoek at mac.com) wrote:


>On Nov 1, 2005, at 7:46 PM, Marco Piovanelli wrote:

>

>> The included WASTE.framework replaces the old static library

>> (libWASTE.a), includes the new WASTE.h header file, and exports

>> all of the non-deprecated APIs defined by WASTE 2.1.

>>

>

>But will you provide a static library again?


The problem with a static library is that there would need
to be one for each C++ compiler. The one for, say, gcc 4.0,
wouldn't work with CodeWarrior 9.x, and vice versa, because
the C++ runtime support is vendor-specific, so attempting to
link the final executable with the wrong library would fail
due to unresolved symbols. This was much less of a problem
before, because WASTE 2.1 was mostly only C.

Packaging WASTE as a framework completely sidesteps this
issue. Also, a framework is very easy to use and link against,
and can be hidden within the application bundle, preventing
the kind of "DLL hell" problems that plague Windows users.

Anyway, if there are reasons why you prefer static libraries
over frameworks, I'll be happy to consider them.

Best regards,


-- marco

--
It's not the data universe only, it's human conversation.
They want to turn it into a one-way flow that they have entirely
monetized. I look at the collective human mind as a kind of
ecosystem. They want to clear cut it. They want to go into the
rainforest of human thought and mow the thing down.



More information about the WASTE-list mailing list