One thing I think would be good is a THROWS attribute on each method in the component. That way you would be forced in some situations to put try/catches around you code.
This would be really good when using/creating 3rd party components. Being a java programmer, Id also like the ability to define interfaces. This would also give you a work around of not being able to do multiple inheritence by implementing multiple interfaces. Pat "Steve Onnis" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > > I am here by starting a wishlist for CFCs > > Here are my few items. > > 1- Ability to declaire multiple types in the "Type" attribute of the > CFARGUMENT tag. Either by using multiple tags or using a list within the > attribute. > > 2- Ability to dynamicly populate the "ROLES" attribute of the CFFUNCTION > tag. > > 3- Friendlier CFINVOKE syntax so you dont have to create the object ovewr > and over for methods in the same CFC. > eg. > > <cfinvoke component="componentsDemo.components.maths"> > <cfinvokemethod method="Average" returnVar="Bla"> > <cfinvokeargument name="Numbers" value="#Numbers#"> > </cfinvokemethod> > <cfinvokemethod method="Sum" returnVar="Bla2"> > <cfinvokeargument name="Calculation" value="#Calculate#"> > </cfinvokemethod> > </cfinvoke> > > > I know you can do this by using the CreateObject and <CFOBJECT methods, but > if they give us these tags to use, maybe they should be a little more > flexible > > my 2 cents > > Steve Onnis > > > > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
