Seems that if you call a file .cfc it jst works as a component. Probably to easily turn a UDF include file into a cfc with no code changes ?

but then the other issue on bd it seems to default to output=false where 6.1 defaults to output=true (id say thats a backwards-compatible thing cos output=false being a default is much nicer.)

Pat





M@ Bourke wrote:
only other difference I had with swapping code between machines was 1
cfc spat an error on BD
when I looked at the code I noticed it had no component tags, but it
worked fine on CF 6.1.

I thought Component tags would be required but it worked fine just
like every other cfc



--- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/

Reply via email to