In their simplest form, cfincludes do not need to fully explain the path
to a file. Relative paths are often sufficient. Or is the code which
makes up your app going to be moving around a lot?
cfincludes are often used to combine sections of reusable code
(typically in a fixed location) to form a complete cf template & process.
If the logic you're "including" seems to be hard to pin down in a single
place of your app, then perhaps what you're dealing with - is really a
cffunction, and not a reusable snippet after all?
Finally, I would frequently confuse the meaning of cfinclude with that
of cflocation during my earlier coding years. Cfincludes use relative
system paths (internal), whereas cflocations use web-based paths
(external) - which frequently use a "web root" variable - because those
may change as your app moves from dev to testing to production.
Al
On 5/29/2012 11:38 AM, Jason King wrote:
Now my question. What's the best way to declare the webroot in front
of any include?
(snipped)
--
online documentation: http://openbd.org/manual/
http://groups.google.com/group/openbd?hl=en
