Ian Laurenson said: > I have been thinking about developing macros for Writer so that Syntax > highlighting occurs, and can select a portion of text and at the click > of a button run an external interpreter.
I tried something like that when I first started writing the document in POD, which is a very simple mark-up language used for Perl documentation. But keeping the code samples separate means that readers get all the code samples to play with, without me having to do any extra work. The reason I'm changing the document is because I read a great book on coding styles. Someone wrote a script that reads in perl and formats it to this coding style. And I'd like to be able to format all my code so that it matches this style. Having the code be external text files means I can run this script on each file and reformat. I'm also trying to make it easier for people to contribute changes to the document, and for me to keep track of what I've changed too, and I think that keeping the code external means I get more fine-grained control through CVS. Rather than having a revision history all in one, monolithic file, I can see revision history on individual pieces. I'm thinking I need to break teh document up into chapters or something so they are separate files as well. That way, I can track changes in the chapter about arrays separate from the changes for the chapter about regular expressions. I know perl pretty well. What I'm still learning is how to manage a large document. Who knows. Maybe the third time around, I'll completely reformat and reconstitute again. Greg -- Hungry for a good read? Crave science fiction? Get a taste of "Hunger Pangs" by Greg London. http://www.greglondon.com/hunger/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
