1) cut and paste all the seperate .spad files back into pamphlet file.
More time wasted than when a Makefile is used with the commands to
extract your .spad files.
Makefile and merging is a one time effort. However the main
thing is actual developement. With separate file you can
compile Spad file and imediately test is (reusing commands
and data from the history). You can try to approximate it
using ')lib' in running FriCAS after 'make'. However,
that means extra commands and context switching compared
to ')compile'. In case of dependencies Makefile is going
to be more complicated: you need to set '$bootStrapMode'
and/or dump databases. Also, to avoid needless recompilation
(simple Makefile will recompile all files contained in a
pamphlet) you need extra logic in Makefile.
I could probably also just put everything into a compile.input file and
call the 'document --tangle=..." command via ")system ..." from inside
fricas. Maybe it would be a good idea to enable something like
)compile graph.spad.pamphlet )domain FGRPH
so that domain FGRPH.spad would be extracted via "document" and compiled
in the usual way.
Anyway, as I said, it was a suggestion and basically the main point I
wanted to make is to use git in a more straighforward way in order to
keep Martin's code closer to trunk as it is now.
Anyone can have the workflow he/she wants. I don't force anyone to
follow my suggestions.
Ralf
PS: I don't think that any code as high-level as Martin's Graph code
should have any need to use $bootStrapMode.
--
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.
