On 7/8/06, Claude Schneegans <[EMAIL PROTECTED]> wrote: > > >>Or at least as a developer, wouldn't you like that? Wouldn't take months > to write a parser then, neh? :-) > > Parsing CF code means that the CF server compiles your code, not YOU. > If you write a parser for some code of yours in CF, it's completely > another story.
See, I was obviously talking about using something BESIDES the CF server to parse the CF code. Presumably CF knows how to parse CF. :-) I don't think XML matters in a closed circle. My point is that CF doesn't generate documentation automatically from source, for instance. Well, actually, it does, for CFCs, so that's a bad example. My main point was 3rd parties parsing CF code. Like how CFEclipse must parse the CF code to offer suggestions, point out errors, etc.. Or how if I wanted to write a perl script to do some majick on a bunch of CF files. Stuff like that. And I was also talking about a human being able to look at code and understand easily what's going on- which is a different beast. Still, what makes some operations easier, makes others harder- it's kinda like Full Metal Alchemist, LOL. I see power in all different ways of doing things... it's just mixing them right, or whatever. :-) ** I can see how I'm not very clear, sorry for the confusion. :DeN ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:245815 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
