<cfinvoke component="12robots" method="isItEvil()">

There, of course, is one other alternative. 

Jason

12Robots wrote:

 

There, of course, is one other alternative. 

Naturally. <cfcomponent extends="12Robots">

Naturally. <cfcomponent extends="12Robots">

You'd still have to invoke the component somehow.

I presumed he meant the new operator.

And, indeed, if it's a persistent component, then there's entityNew() too.

--

Adam

What about using cfinvoke for queries?  All of the projects I've worked on for the current client, I'd say probably 95% of the component/methods I've seen or typed are just for queries.

^_^

(shrug)  Some components have 2-3 functions, some components have 10 or so functions.  Some of the queries are quite large, most of them are just a few lines.

^_^

You're talking about the return value, not what the <cfinvoke> actually does.

And why would you use:

<cfinvoke component="SomeComponent" method="someMethod" returnvariables="someVariable">

When you could just do this:

<cfset someVariable = new SomeComponent().someMethod()>

<cfinvoke> is just a sh!tty, ugly, always unnecessary syntax construct. It's a reminent from when the thinking in CFML was "it's a tag-based language, everything must be done via tags", which was always an illconceived approach to implementing the language.

--

Adam

For the project I'm currently working on, I just switched all the cfinvokes over to variable = new components.componentName().methodName(args) and must admit that reducing code from 10 lines to 3 is pretty nice and easy to read.

I'm sure I'll expand into different things as time goes on.

Thanks, guys.

^_^

Actually, the other alternative I was refering to was to get a decent hosting provider.

jason

Oh you and your lateral thinking...

;-)

--

Adam