However, using those tags means you can't run that CFML on ColdFusion, which as it stands today, is the gold standard for what CFML is. If they were in a separate namespace, and just packaged with the BD CFML runtime, then you could potentially run your code on ColdFusion, either by purchasing a standalone taglib license from NewAtlanta, or by reimplementing the tags yourself (or at least the pieces that you needed).
If/When MM/Adobe were to implement the same features, they could do so as a taglib (to support existing BD code), as well as integrate it directly into the CFML language. As it stands right now, any time I want to use a tag in BD that might not be official, I gotta go digging around in the BD and CF docs and make sure it's a real tag, and not a BD extension. Having the separate taglib would alleviate that need completely. cheers, barneyb On 5/17/05, Dave Merrill <[EMAIL PROTECTED]> wrote: > > You and I disagree about whether an enhancement in BD that isn't > > implemented in CF represents an incompatibility > > Excuse my jumping in. If I'm not mistaken, one area of contention here is > whether when BD adds a tag that cf doesn't support, it should be prefixed > with 'CF' or 'BD'. > > It's arguable both ways IMO. Using BD ensures that it won't conflict with > future cf tags. However, Adobe/MM is obviously aware of BD, and I'd guess > it's pretty likely that they'd either make their new tag compatible with the > existing DB one, or use a different name. Also, using BD permanently flags > the tag as having originated with BD, which IMO isn't a useful semantic > distinction. > > In any event, this doesn't seem like it should be a major source of > friction. > > Dave Merrill > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org
