Date: 02/27/99
- Next message: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Previous message: sas: "[PHP-DEV] CVS update: php3/functions"
- In reply to: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Feb 27, 1999 at 11:02:49AM -0500, Rasmus Lerdorf wrote:
> > There seem to be some open issues in some modules which assume pointers == 32
> > bits wide == int. For example in mysql.c:
> >
> > int type,link;
> > void *ptr;
> >
> > if (index_ptr->type != le_index_ptr) {
> > RETURN_FALSE;
> > }
> > link = (int) index_ptr->ptr;
> > ptr = php3_list_find(link,&type);
> >
> > I'll commit some changes, but people, please bear in mind that a pointer does
> > not necessarily fit into an int. It would be sad, if we would get bug reports
> > related to bad programming behaviour.
>
> Ouch. Never noticed that. Can Purify or some other tool check for these?
>
> -Rasmus
gcc spits out warnings when compiling on a 64bit platform. I've just gone
through its output, but there are some points left:
mysql.c:574
pgsql.c:314 (same as mysql.c)
I don't know what the above logic shall do.
--Regards,
Sascha Schumann | Consultant | finger sas <email protected> | for PGP public key
-- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe <email protected> For help: php-dev-help <email protected>
- Next message: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Previous message: sas: "[PHP-DEV] CVS update: php3/functions"
- In reply to: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Next in thread: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Reply: Rasmus Lerdorf: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

