Bah!
My newsreader is freaking out on replies... Please accept apologies for
null message.
IMO. The resource should be freed upon request, reguardless of refcount.
Further attempts to access the resource would then be in error. This logic
makes sense to me.
If the resource is not released, a warning should be generated.
@OCIFreeStatement would then squash the warning, if this is the desired
behaviour.
""Joe Brown"" <[EMAIL PROTECTED]> wrote in message
9cfi6l$75n$[EMAIL PROTECTED]">news:9cfi6l$75n$[EMAIL PROTECTED]...
>
> "Andi Gutmans" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > At 08:50 PM 4/28/2001 +0200, Thies C. Arntzen wrote:
> > >On Sat, Apr 28, 2001 at 06:12:19PM +0200, Andi Gutmans wrote:
> > > > At 08:28 AM 4/28/2001 -0400, Joe Brown wrote:
> > > > >Having said that,
> > > > >1. is there a good reason OCI shouldn't free the resource
reguardless
> > > of the
> > > > >reference count?
> > >
> > > the problem is that freeing resources that are still in use
> > > will cause trouble once we try to use them (and expect they
> > > are still there)
> >
> > Well it will cause a warning because the resource doesn't exist anymore
> but
> > I don't think it would cause serious problems. In any case, I think
there
> > are two ways to look at this and none is really more correct than the
> other.
> >
> > Andi
> >
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > To contact the list administrators, e-mail: [EMAIL PROTECTED]
> >
>
>
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
