Ard Biesheuvel wrote:
Actually, (un)signed ints are 32-bit on all 64-bit platforms I know of
(Linux/[Free]BSD/Tru64 on Alpha, Sparc64) Don't know about 64-bit PCs,
but I would expect OSes to be consistent across platforms.
Systems are usually
ILP32 - Integer / Long / Pointers 32 bit
or
LP64 - Long
> will have issue. There's also the possibility that some folks are using
> entirely different data types like size_t which can depend on other factors
> such as LFS.
s/size_t/off_t/
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.
On Wed, 16 Jun 2004, Adam Maccabee Trachtenberg wrote:
> On Wed, 16 Jun 2004, Hartmut Holzgraefe wrote:
>
> > > 1) strrpos('abcd', '') returns 4. Expected FALSE
> > Although one could argue whether searching for empty
> > strings makes sense at all the result is not completely
> > wrong. There *is
Rasmus Lerdorf wrote:
On Wed, 16 Jun 2004, Marc Richards wrote:
Going form Apache1 to Apache2, aside form filters (which you mentioned
in bug 27583) there is the default inclusion of mod_ssl and mod_ldap,
better Internationalization features, mod_perl 2.0 (which ONLY works
with Apache2), Subversion
Hello,
In PHP4 and PHP5 the following syntax works fine (note the last comma):
array
(
1 => 'bob',
2 => 'sam',
);
Is being able to have a comma at the END of an array definition a supported
feature, or an undocumented feature that should not be used?
Thanks,
Jason Garber
_
On Thu, 17 Jun 2004, Lester Caine wrote:
> Are we actually looking at development time?
> Perhaps we just need to run test on the alternative platform(s)
> I have two machines running W2k/A2/PHP5RC3/Firebird1.5 which are serving
> up demos, and I've yet to see an error. The SUSE9.1 machine is on th
On Thu, 17 Jun 2004, Jason Garber wrote:
> Hello,
>
> In PHP4 and PHP5 the following syntax works fine (note the last comma):
>
> array
> (
> 1 => 'bob',
> 2 => 'sam',
> );
>
>
> Is being able to have a comma at the END of an array definition a supported
> feature, or an undocumented fea
On Thu, 17 Jun 2004 10:33:39 +0200 (CEST)
Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Jun 2004, Jason Garber wrote:
>
> > Hello,
> >
> > In PHP4 and PHP5 the following syntax works fine (note the last
> > comma):
> >
> > array
> > (
> > 1 => 'bob',
> > 2 => 'sam',
> > );
> >
Rasmus Lerdorf wrote:
On Thu, 17 Jun 2004, Lester Caine wrote:
Are we actually looking at development time?
Perhaps we just need to run test on the alternative platform(s)
I have two machines running W2k/A2/PHP5RC3/Firebird1.5 which are serving
up demos, and I've yet to see an error. The SUSE9.1 ma
Would anyone with Zend karma care to commit this ?
--
Ard
Index: zend_builtin_functions.c
===
RCS file: /repository/ZendEngine2/zend_builtin_functions.c,v
retrieving revision 1.237
diff -u -r1.237 zend_builtin_functions.c
--- zend_bui
I guess "exit();" terminates execution within itself without returning
to the caller, so that is no chance of getting a runtime error.
For example, " return ( exit() ); " is wrong, but works.
Joe Lee
-Original Message-
From: Jason Garber [mailto:[EMAIL PROTECTED]
Sent: Thursday, Jun
Joseph Lee wrote:
I guess "exit();" terminates execution within itself without returning
to the caller, so that is no chance of getting a runtime error.
parse error != runtime error
but language constructs like exit, unset and print are especialy
ment to be as function-like as possible, thats why y
I understand your point, however, this is the way that other languages
behave and its a feature that i consider to be very necessary and
timesaving. My understanding was that Typehinting exists to save having
to do such if-else clauses all the time, since 99.9% of the time, you
will expect an
On Thu, 17 Jun 2004, Jason Garber wrote:
> Is being able to have a comma at the END of an array definition a supported
> feature, or an undocumented feature that should not be used?
If I remember correctly, Zeev or Andi specifically added it as a
result of a user request, so I'd say it's an undoc
On Thu, 2004-06-17 at 11:20, Adam Maccabee Trachtenberg wrote:
> On Thu, 17 Jun 2004, Jason Garber wrote:
>
> > Is being able to have a comma at the END of an array definition a supported
> > feature, or an undocumented feature that should not be used?
>
> If I remember correctly, Zeev or Andi sp
Robert Cummings wrote:
At the end of the array definition or after the last defined array
entry? If the latter... good feature. Hope it's there to stay since it
makes cutting and pasting to arrays a lot easier and various other
automated array building tasks :)
thats exactly what it is in for, savi
committed in ZE2. MFH not needed since this method in ZE1 uses
zend_get_parameters.
"Ard Biesheuvel" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> Would anyone with Zend karma care to commit this ?
>
> --
> Ard
>
>
>
>
> Index: zend_builtin_functions.c
> ==
I guess that was <= 4.1.0 as i get errors at work ( 4.0.x ) and
everything went fine as i misstyped today using 5.0.0rc3 :-)
--red
Adam Maccabee Trachtenberg wrote:
On Thu, 17 Jun 2004, Jason Garber wrote:
Is being able to have a comma at the END of an array definition a supported
feature, or
Hello Ray,
Thursday, June 17, 2004, 3:23:10 PM, you wrote:
> I understand your point, however, this is the way that other languages
> behave and its a feature that i consider to be very necessary and
> timesaving.
In this case PHP behaves like Java very only one pass by reference
is allowed.
This is now [1] a fixed documentation bug :)
I didn't find anything about it in the ChangeLog, nor bugs.php.net,
so I didn't include any version information in the docs.
Drop a mail to the documentation list if you figure it out ;)
didou
[1] -
http://cvs.php.net/diff.php/phpdoc/en/reference/array/
Mehdi Achour wrote:
> This is now [1] a fixed documentation bug :)
> I didn't find anything about it in the ChangeLog, nor bugs.php.net,
> so I didn't include any version information in the docs.
> Drop a mail to the documentation list if you figure it out ;)
>
> didou
>
> [1] -
>
http://cvs.php
At 07:39 AM 6/16/2004 -0400, Ilia Alshanetsky wrote:
Andi,
Well, majority of the places where it is used right now can be abused through
user input.
PHP 4/5: overly long constant names defined(str_repeat("a", 1024 * 1024 * 6));
PHP5: overly long class & method names
PHP5: overly long function name
This is a supported feature as it especially helps with machine generated
arrays.
If it's not documented it should be.
Andi
At 04:03 AM 6/17/2004 -0400, Jason Garber wrote:
Hello,
In PHP4 and PHP5 the following syntax works fine (note the last comma):
array
(
1 => 'bob',
2 => 'sam',
);
Is
Thanks for the good explanation.
~Jason
At 6/17/2004 02:10 PM +0200, Hartmut Holzgraefe wrote:
Joseph Lee wrote:
I guess "exit();" terminates execution within itself without returning
to the caller, so that is no chance of getting a runtime error.
parse error != runtime error
but language construct
Cool. Thanks for updating the docs. I think it will save confusion with
others in the future.
~Jason
At 6/17/2004 11:34 PM +0200, Mehdi Achour wrote:
This is now [1] a fixed documentation bug :)
I didn't find anything about it in the ChangeLog, nor bugs.php.net,
so I didn't include any version i
Morning,
will we have a RC4 or will we simply release the current HEAD as PHP5?
In the last 2 days lots of 64 bit issues were fixed.
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
26 matches
Mail list logo
