17 |
[ttn: This decision to drop support applies to guile-1.6.x; |
[ttn: This decision to drop support applies to guile-1.6.x; |
18 |
guile-1.4.x continues to support this.] |
guile-1.4.x continues to support this.] |
19 |
|
|
20 |
|
[mvo: However, it is not clear yet that there will be a 1.4.x series.] |
21 |
|
|
22 |
Here is more about why "this has been found to be to tricky". It is |
Here is more about why "this has been found to be to tricky". It is |
23 |
about the way it was done, not about why it can't possible at all. |
about the way it was done, not about why it can't possible at all. |
47 |
actually can be recast as an argument for providing access and |
actually can be recast as an argument for providing access and |
48 |
appropriate supporting protocol to `lt_dlsetsearchpath'.] |
appropriate supporting protocol to `lt_dlsetsearchpath'.] |
49 |
|
|
50 |
|
[mvo: Whatever additional tricks libltdl does, they do not apply to ld |
51 |
|
or ld.so. Shared libraries are not only used at run-time (via |
52 |
|
lt_dlopen, say), but also at link-time (by ld) and load-time (by |
53 |
|
ld.so, or whatsitcalledonyourplatform). It might very well be |
54 |
|
possible to design something that is more advanced than |
55 |
|
'load-extension' and plays well with lt_dlopen, ld, and ld.so, |
56 |
|
but limiting us to the very simple things that 'load-extension' |
57 |
|
does now gives us (at least, me) good confidence that it will |
58 |
|
work fairly portably.] |
59 |
|
|
60 |
Additionally, module boundaries are not necessarily language |
Additionally, module boundaries are not necessarily language |
61 |
boundaries. That is, a module can be a mix of Scheme and C (and one |
boundaries. That is, a module can be a mix of Scheme and C (and one |
62 |
file might want to provide more than one module). Therefore, we need |
file might want to provide more than one module). Therefore, we need |
68 |
including failure modes. There are plans to change its interface |
including failure modes. There are plans to change its interface |
69 |
incompatibly. Its registry is opaque (and redundant).] |
incompatibly. Its registry is opaque (and redundant).] |
70 |
|
|
71 |
|
[mvo: It is deliberate that 'load-extension' adds very little over |
72 |
|
dynamic-link/dynamic-call. I don't know of any plans to change |
73 |
|
its interface incompatibly. You can ignore the registry. It is |
74 |
|
there for people who want to statically link extensions.] |
75 |
|
|
76 |
Restricting module system operations and autoloading to Scheme code |
Restricting module system operations and autoloading to Scheme code |
77 |
only provided an immediate and significant simplification, without |
only provided an immediate and significant simplification, without |
78 |
much hassle to the user. The simplified setup should also be easier |
much hassle to the user. The simplified setup should also be easier |
86 |
of this is available w/ guile-1.6.x if configured w/ the |
of this is available w/ guile-1.6.x if configured w/ the |
87 |
"--disable-deprecated" option. None of this is available |
"--disable-deprecated" option. None of this is available |
88 |
in HEAD at this time (2002-05-21).] |
in HEAD at this time (2002-05-21).] |
89 |
|
|
90 |
|
[mvo: Yes, "much hassle" is a subjective term. But there are no |
91 |
|
complaints (besides yours) about it.] |