Argument more or less accepted. But isn't adding illogical behaviour to XML processing playing with the strict compliance philosophy of XML? The example here is a very CF specific example here has a historic reason - CF was built to speed up simple dynamic web applications. So #query_x# inside cfoutput has something almost like a convenience hack.
-nitish 2011/8/20 Alex Skinner <[email protected]> > I don't agree with that, there are a great many examples of what we might > deem illogical behaviour but unfortunately compatibility is important. Take > the following example > > <cfquery datasource="foobar" name="qTest"> > SELECT firstname,surname > from exampleTable > </cfquery> > > Lets say this brings back 2 rows > > <cfoutput> > #qTest.firstname# #qtest.surname# > </cfoutput> > > As we know this outputs the first record, we of course support this but > arguably I should have to either specify the query parameter on the cfoutput > tag or use the array style syntax to output just the first record, I of > course don't have to. To me the XML example adam posts is similar CF guesses > you want the first one. > > My 2p > > Alex > -- > Alex Skinner > Managing Director > Pixl8 Interactive > > Tel: +448452600726 > Email: [email protected] > Web: pixl8.co.uk > > -- > official tag/function reference: http://openbd.org/manual/ > mailing list - http://groups.google.com/group/openbd?hl=en > -- -Nitish "Faith is a free Option" http://www.forcesofindia.com/profiles/np -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
