Is there any particularly deep reason why the build system extracts each
pamphlet into separate .spad files, i.e. one for each
domain/package/category?
I guess (modulo dependency resolution) it should be fine to build one
.spad file from one .spad.pamphlet file and compile that.
Putting everything into separate files ... doesn't that give problems if
someone thinks about defining two domains that mutually depend on each
other? Shouldn't they be compiled in one stroke?
I would be even more happy if we had
.spad.pamphlet -> .spad -> .lsp -> .fasl -> .o
all with the same data. In particular no FOO.NRLIB directories for each
separate constructor. Is this too wild a dream to be achievable in the
near future?
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
