-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> -----Original Message-----
> From: Peter Theobald [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 05, 2000 1:36 PM
> To: CF-Talk
> Subject: RE: TO ALL: Request for ColdFusion SP2 Input
> 
> 
> Here's one:
> 
> I'd like positional parameters to modules. It would make 
> calling a module so much more concise. And I'd like that to 
> extend to CF's built in tags too. For example:
> 
> <cfinclude "mytag.cfm">  instead of <cfinclude
> template="mytag.cfm"> ====================================
> And while we're at it, I often have dozens of one variable 
> outputs that are made too wordy by the syntax: 
> <cfoutput>#var#</cfoutput>. I'd like to see an alternate 


That sounds like a nifty idea, but I suspect it would be rather
unpleasant to implement and somewhat confusing to call (just what
order SHOULD the params be passed in?).

Perhaps an alternate method to get essentially the same functionality
would be to expose ALL of the functionality currently handled by tags
as functions.  That would make <Cfscript> blocks far more powerful as
well.

And while we're talking about <Cfoutput>...  How about just aliasing
<cfoutput> and </cfoutput> to <? and ?> respectively.  Sure it looks
like PHP, but it's easier to deal with...

Not that I would expect any of *that* to happen in a service pack
release.  They're features I'd like to have (especially the
functionalized tags), but I'd rather the coders concentrate on
squishing the bugs in SP2 rather than adding tons of new features...

Regards,
Zac Bedell


-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBOdzMjQraVoMWBwRBEQIb6ACeONxuqAiVCFqDbNJUUfEvmERhZCYAoMp9
S/hg0dvcG8aQpn59dDd9YwYC
=NAga
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to