May 6
In this show we talk about components, application.cfc and a couple other things. We do all this while Dave tries to stay awake.
In this show we talk about components, application.cfc and a couple other things. We do all this while Dave tries to stay awake.
May 8, 2009 at 9:07 AM Well I'd love to call it in, but for now, I'll type it.
The good news: I love the show, guys, keep it up!
The bad news: There were a number of technical errors in this show. The ones I was most troubled with, since I'm basically a CFC ninja, are:
Stated package access is only for inherited children
- package access is for the current directory, a "package" in CF is a folder of CFCs
Stated you cannot write functions in cfscript for components
- they definitely can be used to construct methods for components, but they give you less control
Stated that cfscript functions make a private scoped method
- they make public methods, output=false, but give you no typing (returntype or argument types), and all declared arguments are required. Still, it's very doable.
Stated that Application.cfc was available in CFMX 6
- was added in CFMX 7. Maybe this one's nitpicky.
Hey if you have a number, I'll call it in if you want to play it, or I could even give you an mp3.
Meh, anyways, i like listening, keep pumping them out, thanks!
May 8, 2009 at 11:16 AM Ryan,
Thanks for listening to the show. Thanks for pointing out my errors in the show. I guess doing a show when I was very tired was a bad idea. Obviously I don't have the docs in front of me during the show so I do my best to be as accurate as possible.
The package thing I did not know about. I have never used it in that way so that is probably why.
What I meant to say was that a cfc can't be just cfscript with functions in it.
I don't know what it is, but I ALWAYS get versions mixed up. One of these days I'll get it correct.
Again, thanks for correcting my screw-ups. On a happy note at least it means that someone listened to the show... :)
Thanks,
--Dave
May 8, 2009 at 11:17 AM Ya... 'package' scope definition was wrong in the show...
package = public for cfc's in the same folder and any cfc that extends it.
Glad that Nathan already pointed that out. :)
Jun 18, 2009 at 4:29 PM Another small error as well...
Private methods on the child CAN be called from parent classes that extend that child.
Essentially, 'private' in CFCs really means 'protected'.
Enjoying the show, however!