Date: 02/27/99
- Next message: sas: "[PHP-DEV] CVS update: php3/functions"
- Previous message: sas <email protected>: "[PHP-DEV] PHP3 and 64-bit land"
- In reply to: sas <email protected>: "[PHP-DEV] PHP3 and 64-bit land"
- Next in thread: sas <email protected>: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Reply: sas <email protected>: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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
-- 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: sas: "[PHP-DEV] CVS update: php3/functions"
- Previous message: sas <email protected>: "[PHP-DEV] PHP3 and 64-bit land"
- In reply to: sas <email protected>: "[PHP-DEV] PHP3 and 64-bit land"
- Next in thread: sas <email protected>: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Reply: sas <email protected>: "Re: [PHP-DEV] PHP3 and 64-bit land"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

