> or something similar to keep it as clean as possible? Phil, although I agree that your idea is slightly easier to read, I'm not quite sure it is as easy to parse > Also, is there a agreed upon way to specify custom tags used similar to > included filed (+++)? > well I'd parse all files the same way, simply making a distinction between a required file "+++" versus an optional file "[+++]" There is little need to parse the distinctions between the files since many of the ways of calling a file can be interchanged so easily, so you're left with simply a call method for each file: CustomTag (ie CF_), Include, Module, CFX ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
- RE: Documentation System for Cold Fusi... paul smith
- RE: Documentation System for Cold ... Hal Helms
- RE: Documentation System for ... paul smith
- RE: Documentation System ... Hal Helms
- RE: Documentation System for Cold Fusion McCollough, Alan
- RE: Documentation System for Cold Fusion Lee Borkman
- Re: Documentation System for Cold Fusion John Quarto-vonTivadar
- Re: Documentation System for Cold Fusion John Foulds
- Re: Documentation System for Cold Fusion Lee Borkman
- RE: Documentation System for Cold Fusion Hulsey, James Phillip
- RE: Documentation System for Cold Fusion John Quarto-vonTivadar
- RE: Documentation System for Cold Fusion Nat Papovich
- RE: Documentation System for Cold Fusion Hal Helms
- RE: Documentation System for Cold Fusion Nat Papovich
- RE: Documentation System for Cold Fusion Hal Helms
- RE: Documentation System for Cold Fusion Lee Borkman
- RE: Documentation System for Cold Fusion paul smith
- RE: Documentation System for Cold Fusion Lee Borkman
- RE: Documentation System for Cold Fusion paul smith
