1 |
|
2003-07-24 Gary V. Vaughan <gary@gnu.org> |
2 |
|
|
3 |
|
An experiment: There is loads of code in libm4 which should be in |
4 |
|
the m4 module, but is also used by another module. Just because |
5 |
|
some linkers won't cope with calls across dynamic runtime loaded |
6 |
|
objects I initially left the code in libm4. It will tidy the |
7 |
|
module api immensely if this code moves to the right place, I just |
8 |
|
need to remember to invent a suitable calling mechanism at some |
9 |
|
point. For now, only modules that are statically linked and |
10 |
|
preloaded will get this treatment, so the only platforms that will |
11 |
|
break are those that require all symbols to be resolved at link |
12 |
|
time. |
13 |
|
|
14 |
|
* TODO: Reminder that what I am doing could reduce portability |
15 |
|
unless I do something more robust later. |
16 |
|
* m4/m4module.h (m4_sysval): No longer exported from libm4. |
17 |
|
* m4/utility.c (m4_sysval): No longer declared in libm4. |
18 |
|
* modules/Makefile.am: Reformatting. |
19 |
|
* modules/m4.c (m4_sysval): Declare it at place of use. |
20 |
|
* modules/gnu.c (m4_sysval): Import it for use in esyscmd. |
21 |
|
|
22 |
2003-07-23 Gary V. Vaughan <gary@gnu.org> |
2003-07-23 Gary V. Vaughan <gary@gnu.org> |
23 |
|
|
24 |
* m4/m4module.h: Reformatting and rearranging lines a bit. |
* m4/m4module.h: Reformatting and rearranging lines a bit. |