I have been silently reading the conversation, but I have
to reply on this latest message.
----- Original Message -----
From: "Fred Williams" <[EMAIL PROTECTED]>
Look I'm certain you mean well, but the rest of us are pretty busy using
one of the best small footprint databases on the planet. That means we
are way too busy to nit-pic a good product to pieces, just because it
won't compile clean using Mickeysoft's latest and greatest.
This is unfair. As stated it will actually compile. There are
just warnings to indicate data loss might occur. Which we
all know happens if you convert int64 to a char for example
(Which has nothing todo with the fact that it is a Microsoft
compiler, or Mickeysoft as you call it).
The original poster is (imho) just looking for clarification
if these possible problem spots are working as they are
supposed to, on all platforms. Isn't this a good discussion
to have? To make sure the codebase is at the best quality
it can be? I thought we would all benefit from such a thing,
guess you don't agree.
How' bout you go through this buggy code and fix all your concerns then
upload it to CVS. That way you would be making a huge contribution to
This would mean the original poster has to know every
in and out of the SQLite code. Fixing something that seems
obvious might break something else. Since the original
question was about whether the mentioned warnings are
real I doubt the poster has the knowledge to fix it himself
and no if there are any consequences or not.
us all, and won't come off as such an irritating whiner.
This is just completely rude and uncalled for. If you don't
want to "waste your time" discussing a genuine concern,
then why bother replying at all?
Regards,
Rob Lohman
p.s. funny how you are using "Mickeysoft" Outlook....
