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

Re: [RFC PATCH v2 2/2] MSVC: Fix an "incompatible pointer types" compiler warning

From
Johannes Sixt <j6t@kdbg.org>
Date
Dec 5, 2009, 11:57 UTC
Message-ID
<200912051257.21386.j6t@kdbg.org>
In-Reply-To
<4B1997A0.9000004@ramsay1.demon.co.uk>

[Removed Junio from Cc because IIUC, he prefers to be left out of the loop in Windows related matters until they have settled.]

On Samstag, 5. Dezember 2009, Ramsay Jones wrote:
> The patch is still marked RFC because:
>     - I'm still not sure if the flexibility to support both 32- and 64-bit
>       time_t is required.
>     - should -D_USE_32BIT_TIME_T be added to the Makefile?

If *not* using -D_USE_32BIT_TIME_T produces a build or code base that is in some way superior, why should we require it? For example, its absence could help a 64bit build.

-- Hannes
Previous: Ramsay JonesNext: Ramsay Jones
Message 2 of 6 in “MSVC: Fix an "incompatible pointer types" compiler warning”
  1. 2/2 MSVC: Fix an "incompatible pointer types" compiler warningRamsay Jones, Dec 4, 2009
  2. Johannes SixtDec 5, 2009
  3. Ramsay JonesDec 8, 2009
  4. Johannes SixtDec 8, 2009
  5. Ramsay JonesDec 10, 2009
  6. Johannes SchindelinDec 5, 2009

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.