Re: [2/2] server: Remove a not necessary check for 'current' being not NULL.

[Alexandre Julliard]

Dmitry Timoshkov  writes:
> 'current' is already dereferenced twice before this point.
>
> server/request.c | 23 ++++++++++-------------
>  1 file changed, 10 insertions(+), 13 deletions(-)

You can't do that.

[2/2] server: Remove a not necessary check for 'current' being not NULL.

[Dmitry Timoshkov]

Alexandre Julliard  wrote:
> > 'current' is already dereferenced twice before this point.
> >
> > server/request.c | 23 ++++++++++-------------
> >  1 file changed, 10 insertions(+), 13 deletions(-)
>
> You can't do that.

Is there a reason why? Can 'current' be set to NULL by a request handler?

[2/2] server: Remove a not necessary check for 'current' being not NULL.

[Alexandre Julliard]

Dmitry Timoshkov  writes:
> Alexandre Julliard  wrote:
> > > 'current' is already dereferenced twice before this point.
> > >
> > > server/request.c | 23 ++++++++++-------------
> > >  1 file changed, 10 insertions(+), 13 deletions(-)
> >
> > You can't do that.
>
> Is there a reason why? Can 'current' be set to NULL by a request handler?

Yes.

[2/2] server: Remove a not necessary check for 'current' being not NULL.

[Dmitry Timoshkov]

Alexandre Julliard  wrote:
> > > > 'current' is already dereferenced twice before this point.
> > > >
> > > > server/request.c | 23 ++++++++++-------------
> > > >  1 file changed, 10 insertions(+), 13 deletions(-)
> > >
> > > You can't do that.
> >
> > Is there a reason why? Can 'current' be set to NULL by a request handler?
>
> Yes.

I see that kill_thread() does that if a being killed thread is current.
Thanks.