> we use 5 at the moment
>
I suppose an element of the problem is that CF is typeless, but understands
the concept of boolean. Boolean values are true/false, yes/no and 1/0, so
without a type specification, use of any of these could mean that they
equate.....
Just out of curiosity I did :
<cfset myVar = "Yes">
<cfif #myVar# eq 1>
Equate
<cfelse>
Does not equate
</cfif>
And I got "Equate".... I know its bad CF, but wondered whether CF would tell
me that "Yes" EQ 1 and it did....
> and yes I did get the window solved
>
> made a workaround .. PPk told me you cant create an empty window object
>
Yeah realised that... There was no constructor for the window object. Just
wondered if you'd managed to roll your own "window object" and still use the
new myObject() stuff...
Stephen
--
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]
