On 16 Jun 2009, at 20:49, Lukas Kahwe Smith wrote:
1) its not about "punishing", its about alerting people that they
are relying on stuff that will go away
2) E_DEPRECATE is for development only and only as a check you
enable now and then
3) its off in both of the php.ini's we will ship wi
On 4 Mar 2009, at 15:46, Kenan Sulayman wrote:
Hey Pierre!
Didn't I included the mt_rand function in my tests ?
Quote: "Average of mersenne twister in 8016909 it's is
1073848211.4106 (
corresponding to that in 8503575 it's the avg. is 1073904131.0286)."
The mail was meant to make the rand
On 13 Jan 2009, at 11:36, David Zülke wrote:
Am 13.01.2009 um 11:09 schrieb Alexey Zakhlestin:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain
what
On 13 Jan 2009, at 11:09, Alexey Zakhlestin wrote:
On Tue, Jan 13, 2009 at 12:32 PM, troels knak-nielsen
wrote:
In a recent mail, some kind of issue regarding queryparams was
mentioned (Possibly related to namespaces). Could anybody explain
what
the issue is, or point to where it's discuss
On Friday 07 November 2008 14:47:59 Josh Thompson wrote:
> Johannes Schlüter wrote:
> > On Thu, 2008-11-06 at 22:19 -0600, Josh Thompson wrote:
> >> I don't understand why in the namespaced example no one seems to have a
> >> problem with new A() meaning new \foo\bar\A(), but we can't use the *
> >
On Tuesday 04 November 2008 18:27:43 Steph Fox wrote:
> Hi Stefan,
>
> > Dev writes a script, uses autoload, overrides global class.
> > Distributed to user, that has ns.lookup=On as you propose, user borks his
> > install, lacks the file containing the class, gets the global class ->
> > obscure e
On Tuesday 04 November 2008 17:44:50 Steph Fox wrote:
> We could have an INI_SYSTEM switch.
>
> ns.lookup=Off
>
> means you _have_ to prefix because otherwise resolution will fail with a
> fatal error, but
>
> ns.lookup=On
>
> means that anything not prefixed and not local goes through the full
> l
On Friday 31 October 2008 20:30:13 Rasmus Lerdorf wrote:
> A simpler approach might be to just make the mailing list software
> enforce a 1 email per 24-hour day per user. It would require a bit more
> upfront work to munge the software, but wouldn't require any ongoing
> effort. Moderation can g
On Wednesday 29 October 2008 16:23:55 you wrote:
> Since this affects everybody, it should be opened up to the community, so,
> the internals should put together several options and then open a poll for
> the community to vote on and then use which ever comes out on top.
And the winner is ...
:nev
On Tuesday 28 October 2008 13:41:24 marius popa wrote:
> an semisolution would be an php.ini variable
> like
> NAMSPACE_SEPARATOR="::"
> so if you have an issue with your classes can be reset to "\" or
> whatever with ini_set
Please make this list readonly or at least moderated for non-devs (yes,
On Monday 20 October 2008 20:42:36 Steph Fox wrote:
> > Well, on German keyboards, it's accessible but only by using ALTGR+?,
> > which is not really a comfortable combination.
>
> Useful to know, thanks Philipp.
>
> Any more localized keyboard issues we should know about? Anyone?
>
> - Steph
The
On Friday 17 October 2008 04:02:32 Gregory Beaver wrote:
> Hi Stas,
>
> This is not what is proposed. The E_WARNING is *only* on a name
> conflict. Please re-read or try the patch:
>
> http://pear.php.net/~greg/resolve_conflict.patch.txt
>
> Greg
Any particular reason why it defaults to seeing i
On Wednesday 15 October 2008 11:16:09 Lester Caine wrote:
> THAT is probably why I am asking the question? And may well be key to my
> understanding why converting non OO code into OO code in PHP is so
> problematic. When I was coding in CC++ more heavily libraries did not need
> to be objects and
On Tuesday 14 October 2008 14:10:50 Steph Fox wrote:
> I'm +1 on ripping out and leaving til 6.0. I don't think there is enough
> time between now and the 5.3.0 code freeze to make major changes to the
> language syntax.
Major changes like ripping the feature that most people are looking forward
On Friday 10 October 2008 19:02:25 Stanislav Malyshev wrote:
> Hi!
>
> > 3) Stas proposal
>
> I have two proposals, actually.
[snip]
> 2. Leave functions/constants as they are now, and add the following syntax:
> Class::Name->method()
> for calling static methods (and referring to class constants
On Thursday 09 October 2008 15:13:43 Jarismar Chaves da Silva wrote:
> Ok, nice solution, but I still don't see why json_encode ignores
> protected/private class members. I mean, why we need this feature.
Because, in theory, it shouldn't even be able to see those members?
Regards,
Stefan
--
PH
On Thursday 09 October 2008 15:31:54 Lukas Kahwe Smith wrote:
> well .. i think this is at least the common use case. then again, json
> is an encoding format, and i expect that i can get the same object
> state by decoding. so the expectation to also get non public
> properties in the json encoded
On Monday 29 September 2008 18:05:48 Arvids Godjuks wrote:
> So as prevoius speaker suggested, and I personaly got to conclusion in
> other thread that ":" is ideal. Short, isn't taken.
$a = $b?A:B:C:D;
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.ph
Marcus Boerger schrieb:
Hello Moriyoshi,
actually you should place it as a PHP module. Boost provides core level
stuff and algorithmns and such. This is a highly specialized bridge.
marcus
Just like Boost.Python
(http://www.boost.org/doc/libs/1_35_0/libs/python/doc/index.html) ;)
Regar
On Tuesday 17 June 2008 08:27:37 Arvids Godjuks wrote:
> 2008/6/16 Edward Z. Yang <[EMAIL PROTECTED]>:
> > PHP userland code may not treat strings as first class arrays, but
> > that's certainly how they are represented internally.
> >
> > Anyway, it would be neat if we could get that foreach synta
On Saturday 14 June 2008 15:26:20 Lukas Kahwe Smith wrote:
> On 11.06.2008, at 01:15, Jani Taskinen wrote:
> > Correct me if I'm wrong but wasn't that the last decision we made
> > about it the last time this was brought up? Just undocument it.
> > Totally. It exists, only works with strings (right
On Sunday 01 June 2008 23:32:58 Hannes Magnusson wrote:
> I don't know what else I can say. You asked if someone had objections
> and I replied stating my personal opinion that I find explicit use
> statements in multiple lines more readable.
> I don't really see the point in dropping three charact
On Wednesday 28 May 2008 09:11:50 Antony Dovgal wrote:
> On 28.05.2008 10:44, Rasmus Lerdorf wrote:
> > Today's web developer is
> > typically writing half their app in some variety of Ecmascript, either
> > Javascript or Actionscript and this array syntax is second nature to all
> > those folks.
>
Lester Caine schrieb:
That sounds like just the sort of edge case that Derick is suggesting
needs logging for fixing up. unicode_semantics=on is just another bodge
to to make it happen rather than a solution. I think I understand your
description, and to my eyes it looks like a unicode bug that
If someone could point me to the float->string code, I'd really appreciate
http://lxr.php.net/source/ZendEngine2/zend_operators.c#1075
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Todd Ruth schrieb:
I'm afraid you'll find Pierre's response representative. The
php devs seem to consider the fact that a theoretically perfect
"==" doesn't exist to mean that the improvements that would
cover 99.9% of user issues with float == shouldn't be made.
It could be worse, however.
On Tuesday 29 April 2008 15:34:07 Sam Barrow wrote:
> This will not work, I get an error that the two must be compatible.
> Wouldn't it be a good idea to allow any type hint for a parameter that
> does not specify a type hint?
That would be a bad idea, because it violates a (in my opinion, the) c
Richard Quadling schrieb:
On 12/04/2008, Rasmus Lerdorf <[EMAIL PROTECTED]> wrote:
There is no bug here. Please read:
http://docs.sun.com/source/806-3568/ncg_goldberg.html
-Rasmus
So, would I be right in thinking that the only time type-juggling is
100% successful is between strings and i
On Monday 24 March 2008 20:28:49 Stanislav Malyshev wrote:
> > Beats me, I'm sure posix-based systems don't, but it is called "Uniform
> > Naming Convention" so it's possible somebody might implement it
>
> The fact that it's called "uniform" doesn't mean it works in anything
> but Windows :) In UN
Rasmus Lerdorf schrieb:
Well, I actually have years of experience taking apps and making them
run under my strict default filter. And it tends to not be very many
changes, if any at all. In the O'Reilly case it gets changed to
O'Reilly which for a pure web app is fine. If all input
consiste
Rasmus Lerdorf schrieb:
The alternative of relying on the developer remembering to filter simply
doesn't work. Wietse's taint mode is another approach, but it has
performance implications.
As I said, when the backend does the escaping, you don't have to
remember it.
filtering would fix, or
Jared Williams schrieb:
A lot of people don't use templates, just raw PHP. So having a short tag
escaping would decrease XSS vulnerabilities.
Well, i don't think that would be wise, because then you'd have to watch
if you're inside
I don't understand why need to essentially duplicate all th
Jared Williams schrieb:
Well, it's the same as the "but i can't validate my php source with
xmllint" folks: You're doing it at the wrong point. Escaping should
happen at the point where you assign the var as a temlate var (in my
small template class: $tpl->assign('items', $some_data) wi
Johannes Schlüter schrieb:
Now we have the big issue: Do we want to have short open tags forever?
Well, without tooo much thinking my idea would be to drop "
you can have short stuff without outputting stuff too.
Regards,
Stefan
P.S.
This patch will be the most useful addition to PHP tha
On Thursday 06 March 2008 23:51:47 Edward Z. Yang wrote:
> These examples don't cause any problems because they're not in the
> object context, so $this is just another, ordinary variable. If you
> include'd the files inside something like:
>
> class Foo {
> public function bar() {
> include
On Wednesday 05 March 2008 11:21:14 Richard Quadling wrote:
> But, having just inherited a load of code which are UTF-8 encoded and
> all have a BOM marker, all the BOM markers are being sent to the
> browser. This screws up sessions as output is sent before headers
> (obviously).
>
> The files are
On Thursday 07 February 2008 14:21:15 Dmitry Stogov wrote:
> Thank you for fix.
> I assume now the patch is ready to commit.
> I'll commit it tomorrow in case of no objections.
>
> Thanks. Dmitry.
The comments in the patch look a bit odd (looks like they were pasted to vim
without :set paste).
R
On Wednesday 30 January 2008 20:52:40 Stanislav Malyshev wrote:
> > I don't think the 'FOO' syntax is very obvious either, but I can't think
> > of a better one and if there isn't a commonly known syntax we can steal
> > from another language, then making up our own, no matter what it is, is
>
> We
On Saturday 26 January 2008 18:22:09 Sam Barrow wrote:
> I'm sorry I misunderstood. If specifying like "$var ?: 5" then it should
> throw an E_NOTICE, as this is a conditional that checks the value of a
> variable ($var).
>
> Sebastian, for assigning of a default value is a variable is not set, I
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 31 December 2007 13:48:52 Antony Dovgal wrote:
> Changing PHP's behavior in a backward-incompatible way that would affect
> everyone and *forcing everyone* to use exceptions seems to be really bad
> idea, especially taking into account that y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 25 October 2007 10:52:57 Ford, Mike wrote:
> On 23 October 2007 19:57, Gregory Beaver wrote:
> > The only reason for me is that "use" implies some kind of autoloading,
> > as I suggested in one of my other mails.
>
> H'mm, that's interestin
Antony Dovgal wrote:
> Right, so let's force other people to learn crappy unreadable syntax
> duplicating nice and clear function call
Oddly, this "crappy unreadable syntax" doesn't lead to any confusion or
complaints for newbies of languages like python or ruby, judging from
the IRC channels. And
Andi Gutmans schrieb:
Our preference would be to stick to "import" because I think the perception many will have of
"use" is that it also includes files (just based on some other languages). That said I agree that
compatibility would be an issue here. In fact it's even somewhat of an issue with
Is it possible or feasible to distinguish betwenn parent:: and
NameOfParentClass::? That would allow to push a call "up" while
preserving the called name while not making Class:: mean different
things depending on the location of the call, which is a very bad thing
IMO (it's an effect that may not
On 04/07/07, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
Nor variables naither constants.
They are defined in run-time.
This seems to me like a bit of drawback. Would it be possible to add
compile-time constants, then (like const FOO = 1; outside a class)?
Creating a class inside a namespace for c
On 19/06/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
I don't care about Unicode support, because it breaks things. I suspect
that PHP6 Unicode extension won't give me controls that I have in PHP5 and
PHP4 strings. PHP6 Unicode support is not designed for international
environment. It is designe
Correct me if I'm wrong, but for those "just not possible" cases, a
single version-constant in the source would suffice, right? So it's at
least not inconsistent...
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
IMO, git is a choice worth thinking about for linux-only projects, but
if there are windows clients involved, it's not anymore (last time i
checked, it required cygwin).
At the moment, SVN is a pain in the ass when it comes to merging, but
they claim that it's fixed in 1.5...
Regards,
Stefan
--
On 21/05/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
Latin capital letter A with diaeresis is 00C4. Not C4.
Pay attention in maths, leading zeroes don't change a number.
I wrote two 8bit values. Not two 16bit ones. Interpreter tries to outsmart
me and thinks that I want 00C4, when I write C
Disclaimer: I don't know much about the way unicode is implemented in
php, i have only used it a bit, but i believe i can clear some things
up here.
On 20/05/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
0xC4 and 0x85 are hex codes for latin small letter a with ogonek in utf-8. ą
If script is
This is more a security fix than a new feature.
mysql_real_escape_string using the wrong character set can be a
problem when the charset used by it is sufficiently different from the
one that is put into it.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
Hi,
for debugging i'd use var_dump, which doesn't output ambiguous things.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 23/04/07, LAUPRETRE François (P) <[EMAIL PROTECTED]> wrote:
+1 for '
Just on a side note, the ; before ?> is redundant already, as ?> (or
any other close-tag) will do that implicitely.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.
On 13/04/07, Ron Korving <[EMAIL PROTECTED]> wrote:
Actually it does, since browsers aren't as strict as the standards they
"implement".
Well, then ?> collides also. So the suggestion is to drop everything
but
On 13/04/07, Tomas Kuliavas <[EMAIL PROTECTED]> wrote:
>> Surely we must to keep a setting just because two people in the world
>> use it.
>> I'm afraid their apps won't run on PHP6 anyway because of numerous major
>> changes
>> (already done and still planned), so one more cleanup won't hurt any
On 12/04/07, Antony Dovgal <[EMAIL PROTECTED]> wrote:
Surely we must to keep a setting just because two people in the world use it.
I'm afraid their apps won't run on PHP6 anyway because of numerous major changes
(already done and still planned), so one more cleanup won't hurt anyone.
This isn'
On 22/03/07, Sean Coates <[EMAIL PROTECTED]> wrote:
> function sort_by_key($key) {
For the record, I do like this syntax, but it COULD be rewritten using
current practices (see below).
I know, and it can be done without typing so much:
class SortByKey {
function __call($name, $a) {
On 22/03/07, Christian Schneider <[EMAIL PROTECTED]> wrote:
>> If somebody has a real-life demonstrated NEED for the
>> closures/scoping, by all means, bring it up.
>
> Plain old google brought up:
> http://groovy.codehaus.org/Martin+Fowler's+closure+examples+in+Groovy
> among other hits (Groovy
Please don't. reads much better than in templates.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Steph wrote:
> Hi Stas,
>
>> By pure coincidence, I was doing a bunch of javascript work lately
>> too, and I find [] syntax OK. From readability POV it's not much
>> difference, but much less clutter if you have really massive data
>> array - no array() things which take half of the space.
>
> F
Hi!
If the namespace-approach only covers classes it is implemented
half-heartedly, IMO. I see a lot of "classes" that are just really
collections of static functions, that's what namespaces should cover,
too. And disallowing constants only so that : works is a bad tradeoff...
Regards,
Stefan
--
BC has already been broken, and while BC breaks are OK in major
version changes (4 -> 5), they are not in minor version changes... and
if you change this behaviour again you are not "undoing" a BC break
but you are breaking it again.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mai
If "use interfaces" means that i have to write an interface matching
every public method in my class if i want that strict mode, and
another interface for every inheriting class that adds method, then
that is not a solution. That means code duplication ...
Regards,
Stefan
--
PHP Internals - PHP
For the people who have said "I can not understand why this is a bad thing":
http://en.wikipedia.org/wiki/Liskov_substitution_principle
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 5/16/06, Ron Korving <[EMAIL PROTECTED]> wrote:
bar; // prints 5
$foo->bar = 4; // error
?>
I'm against visible private variables. If they are visible, they are
part of the interface of the class, which means changing the
implementation means a BC break. If this functionality is going in
Antony Dovgal wrote:
> Only if you created it during the call.
>
> function foo(&$arg) {
> }
>
> foo($nonex);
> var_dump(isset($nonex));
> ?>
>
> bool(false)
>
$ php -r 'function foo(&$foo){} function bar(){ foo($var);
var_dump(get_defined_vars());} bar();'
array(1) {
["var"]=>
NULL
}
--
Pierre wrote:
> On Tue, 14 Mar 2006 07:32:15 -0800
> [EMAIL PROTECTED] (Andi Gutmans) wrote:
>
>> Yeah that sounds good. Maybe change UPDATE to UPDATING
>
> First draft commited in:
>
> php-src / README.UPDATING_TO_PHP6
>
> --Pierre
>
Hi,
A few remarks:
This code lacks the emulation for GET
Hannes Magnusson wrote:
> On 3/7/06, Zeev Suraski <[EMAIL PROTECTED]> wrote:
>> A part of the decision was to supply the few lines of code necessary
>> to emulate register_globals in userspace. Volunteers? :)
>>
>
> http://php.is/bugs/register_globals/register_globals.phps :)
>
> - Hannes
>
sc
On 16/02/06, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> In languages where operator overloading is supported, it comes hand
> in hand with strict typing, which wouldn't allow for different values
> for x>y and y
> Zeev
That's not true, Ruby for example has operator overloading, and has no
problems
Andrei Zmievski wrote:
On Feb 2, 2006, at 5:21 PM, Ilia Alshanetsky wrote:
The real test however would be random character access, rather then
sequential scans from start to end :-).
How often do you access random characters in a string vs. sequential
scans? Which is the more likely scenari
ion would be like
function funcname ($p1, $p2, $params = array());
As I said, just a quick suggestion...
Regards,
Stefan Walk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hartmut Holzgraefe wrote:
Jared White wrote:
While ideally it'd be nice to have named parameters used in the core
of PHP, I realize that's probably an impossible task at the moment. So
I agree that the main goal is to allow users to define APIs in PHP
using this feature. If that's all we had,
See http://bugs.php.net/bug.php?id=23110
It's definitely a gotcha, especially if you use switch(){}, as there
is no way to do strict type checking there.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
Would it be a problem to dual-license the extension? So
users/distributors can choose if they want to use it under the PHP
License or under BSD/LGPL/whatever.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 01/12/05, Michael Walter <[EMAIL PROTECTED]> wrote:
> Surely it ought to care iff trying to look like a processing
> instruction. But we digress...
>
> On 12/1/05, Bart de Boer <[EMAIL PROTECTED]> wrote:
> > So, that whitespace is meaningfull for XML. Not for PHP. PHP couldn't care
> > less how
On 26/11/05, Robert Cummings <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-11-25 at 20:07, Ken Tossell wrote:
> > Not to start a flame war, but...
> >
> > How about STD, Std, or something similar? It certainly works for... that
> > language... that has multiple implementations of the standard classes.
On 23/11/05, Edin Kadribasic <[EMAIL PROTECTED]> wrote:
> Marcus Boerger wrote:
> > Hello Stefan,
> >
> >"<%=" is of course also conflicting the XML specs since "<"
> > must be followed by a "!" is we are in a DTD context. Or a "?"
> > to start a processing instruction or a valid element name.
On 22/11/05, Derick Rethans <[EMAIL PROTECTED]> wrote:
> Hello folks!
>
> On 11 and 12 November a bunch of us had a developers meeting in Paris,
> discussing the things we want to do for PHP 6. Partly because of the
> Unicode support, but we also discussed the items on "Rasmus' wishlist"
> and a lo
On 10/4/05, Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Mon, 3 Oct 2005, Greg Beaver wrote:
>
> > > 1. zlib is required now with php, and by default php isn't installed
> > > with zlib nor does configure catch this, so, while make install is
> > > running and when pear is being installed m
On Tue, Jul 27, 2004 at 02:48:28PM -0500, John Coggeshall wrote:
> Notice how 0 and c are switched incorrectly. Attached is a patch to
> zend_operators.c that fixes it.
The Manual says:
> Warning
>
> Be carefull when sorting arrays with mixed types values because sort()
> can produce unpredict
On Sat, Jun 26, 2004 at 08:03:12PM -0700, Jason Davidson wrote:
> Hi, is there a reason that when a child class is instantiated the parent
> class constructor does not get called?
> The obvious workaournd for this is to simply call
> $this->parentConstructor(); in the child class constructor, howev
that was the case, an abstraction layer is
useless.)
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, Mar 26, 2004 at 07:05:15AM -0800, Rasmus Lerdorf wrote:
> On Fri, 26 Mar 2004, Stefan Walk wrote:
> > Oh, and the strpos/str_repeat inconsistency should be 'fixed' too, maybe
> > make strpos an alias to str_pos or alike...
>
> So you are saying strlen() sho
tency you'd go and
make everything conform to ONE naming standard. There's no reason that
methods should be different from functions at all. In a way, functions
are just methods with PHP as the implicit reciever...
Oh, and the strpos/str_repeat inconsistency should be 'fixed' too,
debug_backtrace(; } f(1,3);'
array(3) {
[0]=>
string(4) "file"
[1]=>
string(4) "line"
[2]=>
string(8) "function"
}
Note that if you join() the result of array_keys the args argument disappears in php4
as well...
This is not mentioned in
>
> -Adam
I don't like the term 'functional' there, as it's misleading...
Languages like lisp, haskell, ... are commonly referred to as functional
languages, where languages like C (and non-OO PHP) are referred to as
imperative or procedural. I think that should be rephrase
#x27;.preg_replace('/\r\n|\n|\r/', '$0', $str).'';
}
I think that function is not neccessary... nl2br is already redundant.
They are one-liners in php itself... so no need to write functions for
them.
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals
> ref_count(mixed var)
Just a quick note, do you know debug_zval_dump()?
[EMAIL PROTECTED]:~$ php -r '$a = 2; $b = $a; debug_zval_dump($a);'
long(2) refcount(3)
[EMAIL PROTECTED]:~$
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Inte
er('HTTP/1.1 404 Not Found'); in CGI, just
'Status: 404' is outputted where it should output
'Status: 404 Not Found'
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
.6
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sun, Feb 15, 2004 at 04:12:08PM +0100, Marcus Boerger wrote:
> Even if it were not the best solution it is still the solution that fits PHP
> best and which is easiest to the developers. And as i said a while back the
> current exception class allows several things a user implementation cannot
>
> Stefan Walk: +1 for GMP (GMP's superior)
Just a note - I'm not in favour of installing GMP (or BC) by default, i
just stated that it has better features (and that it's not available on
windows).
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Run
manual says so, i don't use windows).
Stefan
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi!
There is an inconsistency in the Zend API (See #27097) so integers are
reported as "integer" by zend_zval_type_name but "long" by
zend_parse_arg_impl causing confusion for users not knowing C,
the attached patch fixes it.
Stefan
--
Regards,
Stefan Walk
<[EMAIL PROTEC
This has been discussed on internals before.
See http://www.zend.com/lists/php-dev/200310/msg00026.html and
follow-ups.
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, Dec 22, 2003 at 09:34:38AM -0500, Hans Lellelid wrote:
> This was AFAIK the way to invoke methods in a static class. Perhaps we
> now need to specify classname rather than 'self'.
Just use __CLASS__.
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP I
ject)
works here in b3. That's the general notation for static method calls in
callbacks, afaik.
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to admit though that constants
are named in CamelCase usually.)
It's one of the reasons i prefer Ruby over most OO languages out
there...
> Huh? That's awful. Who supports that sort of magic?
That's not much more magic than case-insensitive functions.
--
Regards,
Stefan Walk
&
s from names when calling a
function/method (that would clear up the strpos/str_replace etc
inconsistency as well).
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
even nicer if those literals could be used with
both posix and pcre)...
--
Regards,
Stefan Walk
<[EMAIL PROTECTED]>
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
1 - 100 of 121 matches
Mail list logo
