On Mar 13, 1:42 am, Lex Trotman <[email protected]> wrote:
> To me the latter seems a less intrusive approach and it allows the extra > facility to be turned off if required (Stuart, my security concerns and > Murphys law both require the ability to turn it off, no matter how > transparent the changes are :-) I would rather like to see the straight up / unify of the backend output mechanism *in the end*, because - There is one (extreme) software development philosophy which requires that if you add something, then you should remove something as well, to prevent bloatware. So far, adding another layer on top of template sections and tag entries should only be a temporarily solution. - The current Agile practices, especially Test Driven Development (TDD), http://en.wikipedia.org/wiki/Test_Driven_Development, will ensure precisely backward behaviour compatibility. Since the project Cameron is working on is institute funded, not a temp hack, I have a feeling that Cameron would do extensive testing. Would you Cameron? -- You received this message because you are subscribed to the Google Groups "asciidoc" 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/asciidoc?hl=en.
