Waldek, On Tue, Mar 8, 2011 at 3:09 PM, you wrote: > > Compiler is autoloaded. You need to call 'oldCompilerAutoloadOnceTrigger' > (no arguments) before using compiler. >
Thanks again. That worked perfectly. Here is an example: http://axiom-wiki.newsynthesis.org/SandBoxSTRING2SPAD > BTW: What are you really trying to do? If you want result in memory > than output to string is probably not the best thing -- whith small > change to 'spadCompile' it should be possible to get different kind > of output. > My first application for this is in the Sage interface to FriCAS. I had previously implemented the ability to compile Spad code from the Sage command line and as a consequence more importantly: to include Spad code in Sage Notebook web pages. But managing intermediate source files in a pain, especially in a multi-user environment. This function makes it much easier. I can imagine that it might also be useful in unit testing or in other applications where it is desirable that the FriCAS system be able to dynamically modify the library. I understand your point about the undesirability of just capturing the output of the compiler into a string. Of course the first one might want to know is just the success or failure of the compilation. Beyond that it might be interesting to recover a list of dependencies, specific warning and/or error messages. I think the current Spad compiler output would be seen as abnormally verbose and obscure if it was simply displayed, say to a Sage Notebook user. If you have some ideas about how this sort of programmatic interface to the Spad compiler might be implemented in a more user friendly way then I think it would be great to include it in FriCAS. I would be glad to try to help and to test it. Regards, Bill Page. -- 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.
