workarounds (ok, it wasnt that bad) in CFMX for shared scope vars was
one of the best bug fixes. I've heard other people say, "In case I go
back to cf5", but are many people actually reverting from MX to cf5, or
building for both?
-Ray
> -----Original Message-----
> From: Samuel R. Neff [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 27, 2003 7:56 PM
> To: CF-Talk
> Subject: RE: Scope Locking (RE: Blue Dragon and Fusebox)
>
>
> Care to clarify why?
>
>
> > -----Original Message-----
> > From: Calvin Ward [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 27, 2003 1:09 PM
> > To: CF-Talk
> > Subject: Re: Scope Locking (RE: Blue Dragon and Fusebox)
> >
> > I would opine that locking shared scope variables is still a
> > best practice and not locking shared scope variables is a bad
> > practice, regardless of CF version.
> >
> > - Calvin
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
