On Thu, 5 May 2005, Dave Dodge wrote:
> This may not matter here, but I believe on X86-64 Windows "long"
> remains 32 bits, in order to avoid breaking data structure layout in
On X86_64 Linux 'long' is definitely 64bits - this caused a few
problems with programs that dealt with
Hallo
> On Sun, May 01, 2005 at 09:41:51AM -0700, Steven M. Schultz wrote:
> > On Sun, 1 May 2005 [EMAIL PROTECTED] wrote:
> > A pleasant side effect is that you should have an easier time
> > of building with Cygwin.
> >
> > > Most appear to be type conversions which are not cast ie l
On Sun, May 01, 2005 at 09:41:51AM -0700, Steven M. Schultz wrote:
> On Sun, 1 May 2005 [EMAIL PROTECTED] wrote:
> A pleasant side effect is that you should have an easier time
> of building with Cygwin.
>
> > Most appear to be type conversions which are not cast ie long to uint32_t.
>
On Tue, 3 May 2005 [EMAIL PROTECTED] wrote:
> I can see a number of "sizeof (unsigned int)" which is clearly as you say to
> adapt to
> machine word size, but then the Limits.hh essentially defines a whole list of
> templated
> structures which contain only static member with details about fi
On Mon, 2 May 2005 [EMAIL PROTECTED] wrote:
> I must admit I am curious to know while cygwin g++ reports errors where the
> linux
> compile presumably is only reporting warnings. I cannot see any switch in the
> make files
Hmmm, C++ is weird and not something I'm familiar with.
> Af
On Sun, 1 May 2005 [EMAIL PROTECTED] wrote:
> I had downloaded the CVS but hadn't noticed tha absence of .s files.
> I was not sure if it was a good option to start with.
It is a far better (much newer) starting place. The changes that were
made to get rid of the .s files were
