#30559 [Bgs]: ext/standard fails to compile due to data type error
| From: | derick@php.net | Date: | Wed, 27 Oct 2004 09:48:33 +0000 |
| Subject: | #30559 [Bgs]: ext/standard fails to compile due to data type error | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-68381@lists.php.net to get a copy of this message | ||
ID: 30559
Updated by: derick@php.net
Reported By: jbarwick at sentienthealth dot com
Status: Bogus
Bug Type: Compile Failure
Operating System: *
PHP Version: *
New Comment:
Right, the mbstring stuff definitely needs to be fixed, no argument
there :)
Previous Comments:
------------------------------------------------------------------------
[2004-10-27 11:43:29] jbarwick at sentienthealth dot com
you are right...most of the time my justification is:
"Warning can be safely ignored"
However, I cannot ignore warnings like:
"statement always returns false due to limited range of data type"
cannot ignore this one
....or
"loss of precision due to limited range of data type."
sometimes I ignore this...but have to look.
in the if statement below, it is probably safe to ignore the particular
error that was created.
However, I do like to report them to developers...JUST in case...
Take the mbstring library...for example...TONS of integer math in there
on pointers ... and...seems to be fine on 32 bit systems..but that don't
work on 64 bit pointers.
cheers!
------------------------------------------------------------------------
[2004-10-27 11:07:48] derick@php.net
"Whenever our shop compiles a tool to be used in our business, I must
justify EVERY compiler warning."
What would be the reason for that? It makes no sense in a lot of
cases...
------------------------------------------------------------------------
[2004-10-27 03:55:12] jbarwick at sentienthealth dot com
I understand from your perspective that "this doesn't imply" a bug in
PHP itself. And I concur. I appriciate the info on other sites to
post bugs.
Whenever our shop compiles a tool to be used in our business, I must
justify EVERY compiler warning.
As I appriciate that you "Won't Fix" this, It amazes me that you refuse
to add the most simplistic typecast to something to remove a warning
that just makes people question the code.
Just ONE LITTLE typecast...eh? Well, if var_unserializer.c is a
"generated source"...guess you can't.
Anyway, thanks for listening to one of your advocates of PHP. I guess
I'll keep my diffs around and apply this patch when we go to 4.3.9...
Thanks..
------------------------------------------------------------------------
[2004-10-26 20:54:42] helly@php.net
Sorry, but your problem does not imply a bug in PHP itself. For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system
is not the
appropriate forum for asking support questions.
Thank you for your interest in PHP.
Upgrade your re2c: http://sf.net/projects/re2c
------------------------------------------------------------------------
[2004-10-26 11:28:28] derick@php.net
This is a generated file (by re2c) from var_serializer.re. This is not
an ERROR, but a warning, and something that should be fixed in the re2c
tool. You can safely ignore this warning.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/30559
--
Edit this bug report at http://bugs.php.net/?id=30559&edit=1