-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is work underway to be able to handle this concept
of a package providing native code to other packages.
It is done in several packages already, but it is time
to make the package mechanism extensible and this feature
is one of the motivating e
James Bullard <[EMAIL PROTECTED]> writes:
> Seth, thanks for the advice. This solution seems like it might work,
> but then all errors occur at runtime rather than at compile time.
I'm sure you could still create some compile time errors ;-)
Yes, doing things dynamically means you won't catch nea
Seth, thanks for the advice. This solution seems like it might work, but
then all errors occur at runtime rather than at compile time. This seems
like I am exchanging one evil for another (run time segfaults versus
code duplication) Lets say we have these three package A, B, and C
defined more
Hi Jim,
James Bullard <[EMAIL PROTECTED]> writes:
> I would like to construct two packages (A, B) which utilize a number of
> common C functions. The most straightforward way to do this is just copy
> the relevant .c and .h files from one src directory to the next, but
> this is tedious especia
This might fall under the purview of bundles, but I could not find any
example bundles which demonstrated what I am after.
I would like to construct two packages (A, B) which utilize a number of
common C functions. The most straightforward way to do this is just copy
the relevant .c and .h file
