git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/2] merge-recursive: Workaround unused variable warning

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 18, 2010, 00:10 UTC
Message-ID
<20100818001032.GA7694@burratino>
In-Reply-To
<AANLkTikLXy4gPttmX=wzcDaFAfZO=OEk4PEDKh3sCSOF@mail.gmail.com>
Elijah Newren wrote:
> On Thu, Aug 12, 2010 at 8:09 PM, Elijah Newren <newren@gmail.com> wrote:
Show 6 quoted lines
>> +++ b/merge-recursive.c
>> @@ -1214,6 +1214,7 @@ static int process_df_entry(struct merge_options *o,
>>        /* We currently only handle D->F cases */
>>        assert((!o_sha && a_sha && !b_sha) ||
>>               (!o_sha && !a_sha && b_sha));
>> +       (void)o_sha;
[...]
>                        would a different method of fixing warnings
> when NDEBUG is defined be preferred?  (Maybe changing the
> "assert(foo)" into "if (!foo) die..." instead?)

Yes, that sounds like a good idea. The user would probably benefit from knowing what happened.

Previous: Elijah NewrenNext: Junio C Hamano
Message 4 of 9 in “Fix windows portability issues in en/d-f-conflict-fix series”
  1. 0/2 Fix windows portability issues in en/d-f-conflict-fix seriesElijah Newren, Aug 13, 2010
  2. 1/2 merge-recursive: Workaround unused variable warningElijah Newren, Aug 13, 2010
  3. Elijah NewrenAug 18, 2010
  4. Jonathan NiederAug 18, 2010
  5. Junio C HamanoAug 18, 2010
  6. Elijah NewrenAug 18, 2010
  7. Junio C HamanoAug 18, 2010
  8. Elijah NewrenAug 18, 2010
  9. 2/2 Mark tests that use symlinks as needing SYMLINKS prerequisiteElijah Newren, Aug 13, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.