Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-08-01 Thread Daniel Stenberg
On Tue, 31 Jul 2007, Guenter Knauf wrote: > as we slowly realize it seems that half of the platforms and compilers have > this proplem we know now for sure that the LIBSSH2_APINO is bogus; so I > vote for an immediate removal of it It gets my vote too. We should do things backwards compatib

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-31 Thread Guenter Knauf
Hi, > On Thu, Jul 12, 2007 at 10:43:13AM -0400, James Housley wrote: >> On Jul 12, 2007, at 10:26 AM, Guenter Knauf wrote: >> >> > Hi Jim, >> >>> 200706012030L ? >> > >> >> I would think a LONG would work, or we need to make a second constant >> >> to use, so as not to break the comparison of exis

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-31 Thread Albert Chin
On Thu, Jul 12, 2007 at 10:43:13AM -0400, James Housley wrote: > On Jul 12, 2007, at 10:26 AM, Guenter Knauf wrote: > > > Hi Jim, > >>> 200706012030L ? > > > >> I would think a LONG would work, or we need to make a second constant > >> to use, so as not to break the comparison of existing software

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread Daniel Stenberg
On Thu, 12 Jul 2007, James Housley wrote: >> I think we can shorten this constant to 20070601 in libssh2 since its not >> very likely that we change the libssh2 API more than once a day, or? > > But 20070601 is less then the previous constant, so all existing tests would > fail. You can't chang

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread James Housley
On Jul 12, 2007, at 10:26 AM, Guenter Knauf wrote: > Hi Jim, >>> 200706012030L ? > >> I would think a LONG would work, or we need to make a second constant >> to use, so as not to break the comparison of existing software that >> doesn't have the problem with the long. > when I'm just going to cha

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread Guenter Knauf
Hi Jim, >> 200706012030L ? > I would think a LONG would work, or we need to make a second constant > to use, so as not to break the comparison of existing software that > doesn't have the problem with the long. when I'm just going to change this - I think we should also ask for existance of LIBSS

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread Guenter Knauf
Hi Jim, >> 200706012030L ? > I would think a LONG would work, or we need to make a second constant > to use, so as not to break the comparison of existing software that > doesn't have the problem with the long. I believe that too, and it shouldnt break something; so lets just change it... I start

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread James Housley
On Jul 12, 2007, at 6:58 AM, Mikhail Gusarov wrote: > > Twas brillig at 12:21:37 12.07.2007 UTC+02 when Guenter Knauf did > gyre and gimble: > > GK> ../../curl/lib/transfer.c", line 335.47: 1506-207 (W) Integer > constant 200706012030 out of range. > > 200706012030L ? I would think a LONG wo

Re: [libssh2] preprocessor warning with LIBSSH2_APINO

2007-07-12 Thread Mikhail Gusarov
Twas brillig at 12:21:37 12.07.2007 UTC+02 when Guenter Knauf did gyre and gimble: GK> ../../curl/lib/transfer.c", line 335.47: 1506-207 (W) Integer constant 200706012030 out of range. 200706012030L ? -- JID: [EMAIL PROTECTED] ---