>>>> Try >>>> %---BEGIN aaa.pamphlet >>>> <<*>>= >>>> <<X>> >>>> A >>>> @ >>>> <<X>>= >>>> EFG >>>> @ >>>> <<*>>= >>>> B >>>> @ >>>> <<C>>= >>>> UVW >>>> @ >>>> %---END aaa.pamphlet >>>> >>>> notangle aaa.pamphlet >>>> EFG >>>> A >>>> UVW >>>> B >>> Ugh. I don't think this is a style of LP we should use. >> Why not? Well, it was just an example, but I don't think that a >> continued code junk is a terribly bad idea. I would only require that >> braces are paired within each chunk. > > Non-unique root node definitions in a file will increase complexity. > Ideally all code chunks in a program would have unique chunk names - at > the very least, anything part of a particular tangle operation should > have a unique name. I expect to run tangle once per <<*>> defined, and > I expect one <<*>> per file (or "project" if you prefer.) Perhaps > there are reasons not to do that but I'm not seeing it right now.
Well, amusingly enough, I tried it in cl-web and the code seems to already exhibits the behavior above ;-). So if anyone wants to do that they can. I think I understand better now what you were saying - as opposed to breaking a chunk definition down into sub chunks which are included in a toplevel chunk, you simply have a single chunk with its definition spread through the file, with the scan identifying where the pieces are and putting them together. Cheers, CY _______________________________________________ Axiom-developer mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/axiom-developer
