Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #4819 > unrolled thread

PHP 5.3.9 hex bug?

Back to article view | Back to comp.lang.php

Contents

  PHP 5.3.9 hex bug? "aaa" <aaa@aaaaaaaaaaa.com> - 2012-02-15 16:12 +0100
    Re: PHP 5.3.9 hex bug? tony@mountifield.org (Tony Mountifield) - 2012-02-15 16:36 +0000
    Re: PHP 5.3.9 hex bug? Denis McMahon <denismfmcmahon@gmail.com> - 2012-02-15 16:48 +0000
    Re: PHP 5.3.9 hex bug? "Álvaro G. Vicario" <alvaro.NOSPAMTHANX@demogracia.com.invalid> - 2012-02-15 18:48 +0100
      Re: PHP 5.3.9 hex bug? "aaa" <aaa@aaaaaaaaaaa.com> - 2012-02-16 10:38 +0100
        Re: PHP 5.3.9 hex bug? "Álvaro G. Vicario" <alvaro.NOSPAMTHANX@demogracia.com.invalid> - 2012-02-16 14:08 +0100
      Re: PHP 5.3.9 hex bug? Thomas Mlynarczyk <thomas@mlynarczyk-webdesign.de> - 2012-02-16 12:37 +0100
    Re: PHP 5.3.9 hex bug? "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-02-15 20:00 +0100

#4819 — PHP 5.3.9 hex bug?

Hello,
Why is this:
fseek($f, 0x0000+2, SEEK_SET);
giving same result as:
fseek($f, 4, SEEK_SET);
and not same result as:
fseek($f, 0000+2, SEEK_SET);
or
fseek($f, 2, SEEK_SET);
?
What is wrong with the hex notation?

-- 
A

[toc] | [next] | [standalone]

#4820

In article <jhgi0p$r76$1@speranza.aioe.org>, aaa <aaa@aaaaaaaaaaa.com> wrote:
> Hello,
> Why is this:
> fseek($f, 0x0000+2, SEEK_SET);
> giving same result as:
> fseek($f, 4, SEEK_SET);
> and not same result as:
> fseek($f, 0000+2, SEEK_SET);
> or
> fseek($f, 2, SEEK_SET);
> ?
> What is wrong with the hex notation?

What does it give you if you just print the expressions instead?

Cheers
Tony
-- 
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org

[toc] | [prev] | [next] | [standalone]

#4821

On Wed, 15 Feb 2012 16:12:43 +0100, aaa wrote:

> Hello,
> Why is this:
> fseek($f, 0x0000+2, SEEK_SET);
> giving same result as:
> fseek($f, 4, SEEK_SET);
> and not same result as:
> fseek($f, 0000+2, SEEK_SET);
> or
> fseek($f, 2, SEEK_SET);
> ?
> What is wrong with the hex notation?

from "http://uk.php.net/manual/en/function.fseek.php" we find that "Upon 
success, returns 0; otherwise, returns -1."

Perhaps the problem is actually with "what happens next" when taken in 
the context of "what the file contains".

Rgds

Denis McMahon

[toc] | [prev] | [next] | [standalone]

#4823

El 15/02/2012 16:12, aaa escribió/wrote:
> Why is this:
> fseek($f, 0x0000+2, SEEK_SET);
> giving same result as:
> fseek($f, 4, SEEK_SET);
> and not same result as:
> fseek($f, 0000+2, SEEK_SET);
> or
> fseek($f, 2, SEEK_SET);
> ?
> What is wrong with the hex notation?

It's really funny:

	var_dump(0x0 + 2, 0x0+ 2, 0x0+2, 0x0 +2);

... prints:

	int(2)
	int(2)
	int(4)
	int(4)

No idea of what's going on but it only seems to affect hexadecimal zero 
so at least there's an obvious workaround.


-- 
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--

[toc] | [prev] | [next] | [standalone]

#4829

> It's really funny:
>
> var_dump(0x0 + 2, 0x0+ 2, 0x0+2, 0x0 +2);
>
> ... prints:
>
> int(2)
> int(2)
> int(4)
> int(4)
>
> No idea of what's going on but it only seems to affect hexadecimal zero so
> at least there's an obvious workaround.

Yeah. I already reported that bug to PHP guys, so perhaps 5.2.11 will have
it fixed.
I spent like 5 hours trying to figure out what's wrong with my code ;/

-- 
A

[toc] | [prev] | [next] | [standalone]

#4835

El 16/02/2012 10:38, aaa escribió/wrote:
>> It's really funny:
>>
>> var_dump(0x0 + 2, 0x0+ 2, 0x0+2, 0x0 +2);
>>
>> ... prints:
>>
>> int(2)
>> int(2)
>> int(4)
>> int(4)
>>
>> No idea of what's going on but it only seems to affect hexadecimal zero so
>> at least there's an obvious workaround.
>
> Yeah. I already reported that bug to PHP guys, so perhaps 5.2.11 will have
> it fixed.

And it seems it's a valid bug: https://bugs.php.net/bug.php?id=61095



-- 
-- http://alvaro.es - Álvaro G. Vicario - Burgos, Spain
-- Mi sitio sobre programación web: http://borrame.com
-- Mi web de humor satinado: http://www.demogracia.com
--

[toc] | [prev] | [next] | [standalone]

#4830

Álvaro G. Vicario schrieb:
> It's really funny:
> 
>     var_dump(0x0 + 2, 0x0+ 2, 0x0+2, 0x0 +2);
> 
> ... prints:
> 
>     int(2)
>     int(2)
>     int(4)
>     int(4)

This bug does not seem to occur with PHP 5.2 (Tested with 5.2.12). So it 
was probably introduced with PHP 5.3 (and is still present in 5.4.0alpha3).

Greetings,
Thomas

-- 
Ce n'est pas parce qu'ils sont nombreux à avoir tort qu'ils ont raison!
(Coluche)

[toc] | [prev] | [next] | [standalone]

#4825

Am 15.02.2012 16:12, schrieb aaa:
> Hello,
> Why is this:
> fseek($f, 0x0000+2, SEEK_SET);
> giving same result as:
> fseek($f, 4, SEEK_SET);
> and not same result as:
> fseek($f, 0000+2, SEEK_SET);
> or
> fseek($f, 2, SEEK_SET);
> ?
> What is wrong with the hex notation?
> 

About hex numbers and strings of hex numbers see thread
"Implied cast differs from explicit cast".

It looks like PHP is not very consistent there.

/Str.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.php

csiph-web