Re: [ob] remote.c, eliminate unused variables

[Michael Snyder <msnyder@vmware.com>]

Pedro Alves wrote:
> On Wednesday 05 May 2010 22:14:17, Michael Snyder wrote:
>> Pedro Alves wrote:
>>> On Wednesday 05 May 2010 21:46:55, Michael Snyder wrote:
> 
>>>> --- remote.c    5 May 2010 15:05:57 -0000       1.405
>>>> +++ remote.c    5 May 2010 20:43:46 -0000
>>>> @@ -2512,8 +2512,8 @@ remote_threads_info (struct target_ops *
>>>>         {
>>>>           struct gdb_xml_parser *parser;
>>>>           struct threads_parsing_context context;
>>>> -         struct cleanup *back_to = make_cleanup (null_cleanup, NULL);
>>>>  
>>>> +         make_cleanup (null_cleanup, NULL);
>>> Are you making sure (in all your patches) that the reason the
>>> variables are unused isn't itself a bug? 
>> Can't guarantee it, no.
>> I'm making sure the semantics isn't changed, but I can't always
>> be sure that the original semantics was right.
> 
> Well, then I'll ask please, don't "fix" more things like this,
> and surely don't call it obvious.  You're removing a warning for
> the sake of it. 

No, I'm attempting to make the code easier to understand by
removing dead code and variables.  Since this warning is
turned off, I'm not even reducing the number of warnings.

> A warning is useful as a hint at something 
> wrong with the code; there may be something genuinely wrong
> with it.  Removing it blindly removes the useful hint. 

There's no hint if the warning is turned off.  If I hadn't
touched it and you hadn't reviewed my change, it would have
remained undiscovered indefinitely.

So let's fix it, shall we?  I'll post a separate patch for you to review.


> If you
> want to be bothered to look at the code to see if there's
> something else genuinely wrong, then please, don't change it.

That's not fair, I did "bother" to look at the code.
One got by me, that's all.  Thanks for catching it.