On 10.02.15 01:52, Yasuo Ohgaki wrote:
> Some of you are tired with this topic, but please take a look the RFC
>
> [RFC] Script only includes - this is 3rd version.
> https://wiki.php.net/rfc/script_only_include
>
> Please let me know what you like or dislike.
How exactly does this detection wor
> 2015-02-13 13:50 GMT-03:00 Nikita Popov :
>> use PhpParser\NodeVisitorAbstract;
>> use PhpParser\Error;
>> use PhpParser\Node;
>> use PhpParser\Node\Name;
>> use PhpParser\Node\Name\FullyQualified;
>> use PhpParser\Node\Stmt\Namespace_;
>> use PhpParser\Node\Stmt\Use_;
>> use PhpParser\Node\Stmt\
Hi,
On 19.02.15 10:09, Joe Watkins wrote:
> Morning internals,
>
> The expectations RFC is now in voting phase:
> https://wiki.php.net/rfc/expectations#vote
- I somehow miss information what the exact differences are to the
current implementation, to better judge the impact.
- how does zend
On 19.02.15 16:23, Dmitry Stogov wrote:
>>
>> - how does zend.assertions and assert.exceptions work with
>> "assert_options()" , i.e. isn't the exception behavior meant to be an
>> addition to assert_options() too ?
>>
>
> zend.assertions control assert() compilation and execution
>
> zend.asser
On 19.02.15 22:40, Adam Harvey wrote:
> Those of you with long memories will remember that I proposed a
> Comparable interface way back in the pre-5.4 days, but withdrew it
> when it became obvious that there was no consensus for it as a feature
> and that a vote was likely to fail.
>
> RFC: https
On 20.02.15 18:16, Dan Ackroyd wrote:
> On 20 February 2015 at 12:54, Niklas Keller wrote:
>> Hi internals,
>>
>> It would really make sense to vote on this RFC after there has been a
>> vote on https://wiki.php.net/rfc/context_sensitive_lexer.
>
> That is an understatement:
> https://github.com/
On 20.02.15 18:55, Sara Golemon wrote:
> Announcing this in its own thread:
> https://wiki.php.net/rfc/reserve_even_more_types_in_php_7
>
> This RFC acts as an addition to Levi's
> https://wiki.php.net/rfc/reserve_more_types_in_php_7 by creating a
> forum for voting on additional types not include
On 20.02.15 18:55, Sara Golemon wrote:
> Announcing this in its own thread:
> https://wiki.php.net/rfc/reserve_even_more_types_in_php_7
>
> This RFC acts as an addition to Levi's
> https://wiki.php.net/rfc/reserve_more_types_in_php_7 by creating a
> forum for voting on additional types not include
On 21.02.15 06:11, Thomas Punt wrote:
> Hello Internals!
> The following RFC aims to make empty() have a variable arity:
> https://wiki.php.net/rfc/variadic_empty. This is a simple feature that
> enables for a short-hand notation of checking multiple expressions for
> emptiness (which is a prett
Hi Zeev,
On 21.02.15 18:22, Zeev Suraski wrote:
> I’ve been working with François and several other people from internals@
> and the PHP community to create a single-mode Scalar Type Hints proposal.
>
> I think it’s the RFC is a bit premature and could benefit from a bit more
> time, but given th
On 01.03.15 13:53, Rowan Collins wrote:
> On 1 March 2015 11:29:49 GMT, Yasuo Ohgaki wrote:
>
>> How about rename all of these functions according to CODING_STANDARD
>> for
>> PHP7
>> and have aliases for old names?
>
> If this list had an FAQ (which I think it should), this would be on it.
>
Hello!
On 01.03.15 21:19, Yasuo Ohgaki wrote:
>>> The answer is no, it's just not worth it. Having a function called
>> str_pos which is an alias of strpos, but only on some versions, is more
>> confusing, not less.
>>
>> My sentiment too. Factor in that someone already using the proposed
>> himse
On 03.03.15 00:10, Yasuo Ohgaki wrote:
> I would love to have new & clean APIs.
>
> Please think my proposal as legacy API cleanups. Many of candidates will
> remain
> without CORDING_STANDARSDS confirmed names almost forever. This is what
> I would like to improve. If you don't care about legacy
On 11.03.15 22:28, Bob Weinand wrote:
> after all, some people are not happy with the current proposals about scalar
> types. So, they both still possibly may fail.
>
> Thus, I'd like to come up with a fallback proposal in case both proposals
> fail:
>
> https://wiki.php.net/rfc/basic_scalar_ty
On 15.03.15 16:46, Nikita Popov wrote:
> To ensure we have no shortage of new RFC votes...
>
> https://wiki.php.net/rfc/reclassify_e_strict#vote
>
> Voting is open for ten days :)
>From the RFC:
"Signature mismatch during inheritance
...
Possible alternative: Convert to E_DEPRECATED, if we
Hi Matteo,
On 16.03.15 12:43, Matteo Beccati wrote:
> On 15/03/2015 19:30, Matteo Beccati wrote:
>> In PHP4 times it was in fact quite common to change inherited method
>> signatures to bend them to one's will and/or remove parameters and
>> hardcode them in the parent constructor call. We now kno
On 21.05.2015 03:15, Scott Arciszewski wrote:
> I've just opened an RFC for precisely this purpose:
> https://wiki.php.net/rfc/libsodium
>From https://github.com/jedisct1/libsodium-php :
// Binary to hexadecimal
$hex = Sodium::sodium_bin2hex($bin);
// Hexadecimal to binary
$bin = Sodium::sodium_
On 06.03.2012 00:08, Lester Caine wrote:
The ISP hosting these sites has not got back to me yet, but it would
seem that when they updated from 5.3.9 to 5.3.10 they also switched off
short_open_tag when previously it had been on.
I've learned it also the hard way the ISPs or Hosters did change I
Sebastian Bergmann wrote:
Lukas Smith wrote:
http://bugs.php.net/bug.php?id=30235
I agree with Marcus: self is bound at runtime, so the behaviour is
correct. If you do not like this late binding just do not use self but
the name of the class.
Sorry to jump in the middle, but I've similiar quest
Marcus Boerger wrote:
I agree with Marcus: self is bound at runtime, so the behaviour is
correct. If you do not like this late binding just do not use self but
the name of the class.
Sorry to jump in the middle, but I've similiar question to constants
defined in classes.
When the class is named
Jason Sweat wrote:
When the class is named SomeLongNameBecauseWedontHaveNamespaces and I
define a SELF_EXPLAINING_CONSTANT_NUMBER_ONE I've to write
SomeLongNameBecauseWedontHaveNamespaces::SELF_EXPLAINING_CONSTANT_NUMBER_ONE
to access it from within the class itself.
Is there a way to reference con
Hi,
attached is a patch to add the getParent() method for the tidyNode
against HEAD.
It's just a quick patch for me. I don't know if all tidy version support
the getTidyParent function and if it's memory leak free so someone
should review it first.
cheers,
- Markus
? tidy_getParent.diff.tx
1 PM 7/15/2005 -0400, John Coggeshall wrote:
I'll take a look at it and commit if it looks good.
John
On Fri, 2005-07-15 at 12:09 +0200, Markus Fischer wrote:
> Hi,
>
> attached is a patch to add the getParent() method for the tidyNode
> against HEAD.
>
> It's jus
Derick Rethans wrote:
As type hinting is a new OO thing, it might perhaps make some sense to
make this an exception instead - as this error might also happen for
dynamic things by people who use the classes you designed. In that case
having this fatal error to stop the whole application can be
This is also apply if you use the reference operator?
foreach ($data as &$lines) { ..
?
- Markus
Wez Furlong wrote:
foreach() 'copies' $data, and it's the copy that isn't going away.
--Wez.
On 8/10/05, Ron Korving <[EMAIL PROTECTED]> wrote:
"Derick Rethans" <[EMAIL PROTECTED]> schreef in
Zeev Suraski wrote:
At 20:53 22/08/2005, Marcus Boerger wrote:
> So in that case, the implementation in zend_error_cb() should simply
call
> the user error handler if it's available, or treat it as if it's
E_ERROR if
> there is no user error handler.
Isn't an E_ERROR by default good enough o
31 PM 7/15/2005 -0400, John Coggeshall wrote:
I'll take a look at it and commit if it looks good.
John
On Fri, 2005-07-15 at 12:09 +0200, Markus Fischer wrote:
> Hi,
>
> attached is a patch to add the getParent() method for the tidyNode
> against HEAD.
>
> It's just a q
Hi,
attached the initial email to the list with the patch.
I've been running this now since July in a web crawling application
which runs every day and had no problems. The application is CLI based
and runs for some hours everytime without any sign of memory leaking.
However my c knowledge is
Hi,
Andreas Korthaus wrote:
Lukas Smith wrote:
I dont see a pressing need for an OO API and I also dont think that
PHP internal API's should one by one be moved over to an OO interface
either.
IMO date is a very good example where a nice OO API is very useful -
particularly for people wit
Sebastian wrote:
Good code is code that's easy to debug (among other things). By
removing the "Invalid argument supplied for foreach()" warning without
providing mechanisms to turn it on, debugging code will be more
difficult. Logically speaking, when does it make sense to iterate over
something
Matteo Beccati wrote:
I newly subscribed to this ML after some time I didn't follow it, so I
beg pardon if I'm posting a question that was already discussed.
As you know, a few days ago PHP 4.4.1 was released. As current admin of
a widely used PHP project called phpAdsNew, I discovered just to
Wolfgang Drews wrote:
I don't think it would reduce the number of attacks turning the
version information off. But it would be more cumbersome to help
people with php issues as the php version is not directly available.
Right, that was my point too.
yes, but in the end it is more a problem
Hi,
I'm missing the functionality to get a list of registered hash functions
so one can probe whether a certain hash function is available or not.
- Markus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Jessie Hernandez wrote:
We have two options here:
1) Do not allow constants in namespaces, just stick to functions and
classes.
2) Forget about this inconsistency.
I understand your point of view, but it seems crazy to me to use "\", an
operator that makes absolutely no sense at all and will
Kevin Brown wrote:
The only scripts that would break (far from "trillions") here would be
those where you had a space-less ternary statement comparing two
constants (NOT namespace constants -- they don't even exist yet), as
in the following case:
define('foo','odd');
define('bar','even');
$var =
Marcus Boerger wrote:
Hello Stanislav,
Monday, November 28, 2005, 9:10:55 PM, you wrote:
Why should it be final? Extending it won't do any problem AFAIU.
If it is not final you could derive the config class and then instanciate
it. Static classes which nicely fit into configuration stuff can n
Hi,
any chance for http://bugs.php.net/bug.php?id=34023 this time?
thanks,
- Markus
Markus Fischer wrote:
Hi,
can this be taken into consideration for HEAD now that RC1 is out of the
door?
thanks,
- Markus
Andi Gutmans wrote:
We're in a feature freeze so please hold it to after 5.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Greg Beaver wrote:
> Benjamin Schulz wrote:
>> Of course i want to refer to my own exception in my application or
>> framework as "Exception", and of course i want to use it without
>> prefixes (import myStuff::Exception AS MyStuffException), i wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Ezequiel Gutesman wrote:
> Going back to Stefan's example:
>
>> $sql['id'] = mysql_real_escape_string($_GET['id']);
>> $query = "SELECT * FROM table WHERE id=".$sql['id']
>
> It is true that GRASP won't raise an alarm unless $sql['id'] has
> non
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Daniel Brown wrote:
> I don't know about how it worked for anyone else, but the tables
> didn't display properly on Gmail, so I had a hard time keeping up with
> the performance differences. If you have this in a separate file,
> could you se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
yes exactly, there was no PDF attachment. Interestingly the signature
was a separate attachment ...
thanks
- - Markus
Daniel Brown wrote:
> Markus,
>
> If for some reason the PDF attachment didn't come through to you
> on the list, let
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Rasmus Lerdorf wrote:
> We should probably have done it this way right from
> the beginning, but since we didn't and since we don't really want to
> deal with the potential BC issues of changing working code, we have to
> add it as an option at th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For the record, I'm all for it. Optionality means flexibility. If one
doesn't want to use it, he doesn't have to.
Can you send a patch against 5.3 in CVS?
Have you thought about type hinting for return values?
thanks,
- - Markus
Sam Barrow wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
it would really be great if this could be part of CVS alredy. The patch
doesn't compile currently, I get zillions of
Zend/zend_execute.o: In function `gc_zval_check_possible_root':
php5.3-200712250730/Zend/zend_gc.h:175: undefined reference to
`g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, I got the message :-)
Sorry for interruption, thanks, works as expected.
- - Markus
Dmitry Stogov wrote:
> ./buildconf --force
> ./config.nice
> make clean
> make
>
> Dmtiry.
>
> Markus Fischer wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I started a scratch project with this patch and working with it seems
intuitive so far.
My only question at the moment is the following, however I guess it
isn't specific to your NS patch then to Dmitry's:
My current practice to declare an inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Greg,
Greg Beaver wrote:
> It is technically possible to fix this, on first glance it would involve
> having the lexer return a T_STRING for any non-whitespace following
> T_INTERFACE or between T_IMPLEMENTS and '{'. It would also need to
> return
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I'm monitoring this subject closely because for me and my inner Zen,
having type hint next to namespaces is one of *the* things I'm looking
forward.
Now the current subject was only about return values, for me I'm looking
for the big picture,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, second time me ...
Markus Fischer wrote:
> Hi Greg,
>
> Greg Beaver wrote:
>> It is technically possible to fix this, on first glance it would involve
>> having the lexer return a T_STRING for any non-whitespace follow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Alain Williams wrote:
> On Thu, Jan 03, 2008 at 12:21:21PM -0500, Sam Barrow wrote:
>> I think E_WARNING would be appropriate. That's what happens when you
>> omit an argument to a function right?
>
> The other thing to note about type hinting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
you're right. However to me it's an unimportant factor but maybe not for
the ones who don't like to see type hints (but I don't know what there
arguments are).
thanks,
- - Markus
Stanislav Malyshev wrote:
>> But with the current situation it fee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Stanislav Malyshev wrote:
>> When the type hint says I want an integer, then only integer should be
>> accepted; no casting should be done. It may give predictable results
>
> Why people that want Java just don't use Java I wonder? PHP never was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Sam, Jochem,
Sam Barrow wrote:
> I think we should stick with E_WARNING for now. If you want to use
> exceptions you can throw one in a custom error handler. I can change
> about 4 lines of code in my patch to have it emit an E_WARNING easily.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stanislav Malyshev wrote:
>> You aren't making it a strict static typed language. All that you are
>> doing
>> is saying that at certain points (function entry) that the values are
>> checked
>> and converted to certain types. If within the fuction an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Robert Cummings wrote:
| On Fri, 2008-01-04 at 11:52 -0800, Stanislav Malyshev wrote:
|>> Good point. We were fine before OO and exceptions too weren't we.
|> No, actually we weren't as fine. OO allowed for application frameworks
|> and libraries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Mike Lively wrote:
| in the neck to use effectively. If you start using 'int' type checks for
| functions you are going to want to be passing data from _GET, _POST, etc
| to, you will have to do is_numeric checks or something similar, so
| instea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
accidentally I came across settype() in ext/standard/type.c which says
~ } else if (!strcasecmp(new_type, "float")) {
~convert_to_double(*var);
~ } else if (!strcasecmp(new_type, "double")) { /* deprecated */
~convert_to_double(*var);
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mikko Koppanen wrote:
| I have not been following very closely this conversation so this might
have
| been answered already:
|
|
| $b = '5';
|
| function foo( int &$a )
| {
| echo gettype( $a );
| }
|
| foo( $b );
|
| echo gettype( $b );
|
|
| what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Hannes Magnusson wrote:
| No, the comment is correct.
|
| "for historical [read: BC] reasons "double" is returned in case of a
| float, and not simply "float""
|
| See http://docs.php.net/settype && http://docs.php.net/gettype
Thanks for the poi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pierre wrote:
| That can be a good compromise and may make happy the cons camp.
| However, I would not like to have "11an" returns 0 but raises an
| error. I can live with "[0-1.]" being converted to integer or float as
| it is the case now. Even I wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alain Williams wrote:
|> Pierre wrote:
|> | That can be a good compromise and may make happy the cons camp.
|> | However, I would not like to have "11an" returns 0 but raises an
|> | error. I can live with "[0-1.]" being converted to integer or float
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Hannes Magnusson wrote:
| It means that in PHP the type name is 'float' and referred to as
| 'float' throughout the manual
| For convenience you can use "double" (is_double($f), (double)$f,
| settype($f, "double")..), just like you can use is_int
-1
Readability degrades quite a lot.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
Andi Gutmans wrote:
I think if the syntax is confusing we can go for just a single quote as
part of the operator which doesn't make it look like just another plain
old string, e.g.:
$bar =<<<'FOO
Such a thing is not nice for casual string syntax highlighting in editors.
Needs a special r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
sorry to jump into here
Marcus Boerger wrote:
| I spoke about you as you left no room for discussions. You are not willing
| to compromise in any way, nor are you willing to be productive in any way.
| So there is no way in keeping you in d
+1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Tomi Kaistila wrote:
No one seems to have answered my point that actually relying on type
juggling for anything other than string concatenation is asking for a
problem.
Probably because there isn't a way to answer that point. Anyone who does would
be laughed out of the barn. Like I told Sam just
Markus Fischer wrote:
+1
I didn't realized it until I read Rasmus' mail. In this case, -1 to not break
BC.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
chris# wrote:
$var = [[[HERE
Is just another idea
HERE
I don't like it because this easily breaks editors detecting of
starting/ending brackets. Advanced editors allow jumping forth/back
between start/ending brackets and this would break it.
- Markus
--
PHP Internals - PHP Runtime Dev
Jan Schneider wrote:
Zitat von Jingcheng Zhang <[EMAIL PROTECTED]>:
Hello,
Is there any chance that dirname(__FILE__) being exposed as a constant,
i.e. __DIRNAME__?
No. Constants are per request, dirname(__FILE__) is obviously different
per file.
That's not entirely true, isn't it? Think
Pierre Joye wrote:
On Feb 13, 2008 4:47 PM, Lars Strojny <[EMAIL PROTECTED]> wrote:
Hi everyone,
the following patch[1] adds the functions append_include_path() and
prepend_include_path(). These function are there to make include path
adjustments easier than it is. Especially append_include_pat
Lars Strojny wrote:
Am Donnerstag, den 14.02.2008, 00:56 +0100 schrieb Jochem Maas:
I think Lars has a point ... maybe set_include_path() could
be given a second parameter instead to mitigate the need for seperate
funcs?:
set_include_path('foo', INCPATH_OVERRIDE); // default
set_include_path('f
Lukas Kahwe Smith wrote:
On 14.02.2008, at 10:20, Markus Fischer wrote:
Personally I never understood why we've set_include_path in the first
place anyway. "ini_set('include_path', ..." does exactly the same and
the C function does actually exactly this.
Short histo
Hey,
Paul van Brouwershaven wrote:
I think it should be usefull to add the "PHP mail() header patch" from
Steve Bennett in safemode by default.
I wonder how this would go along with:
http://www.php.net/~derick/meeting-notes.html#safe-mode
I don't know if this still applies, it's from 2005 .
Hi,
generally asking, how would Reflection act on traits? Can this be
detected or will the information be lost after a class has been
assembled? E.g. detect if a certain method comes from a trait and which one?
lG
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Markus Fischer wrote:
generally asking, how would Reflection act on traits? Can this be
detected or will the information be lost after a class has been
assembled? E.g. detect if a certain method comes from a trait and which
one?
Dammit, sorry, I didn't intended to send it to all indivi
Hi,
Hannes Magnusson wrote:
According to Google Code Search (
http://www.google.com/codesearch?q=lang%3Aphp+break\s%2B\%24&hl=en&btnG=Search+Code
) there are only two distinct pieces of code out there using dynamic break:
"never heard of" XPath.class.php and "also never heard of" some code
Hi,
naming classes/function is really an important concern and I'm happy that such
a thing gets a dedicated thread finally.
Stanislav Malyshev wrote:
internationalization capabilities of the ICU library to PHP 5,
specifically 5.2.x and 5.3.x branches. We felt that as PHP gets more and
Is t
Hi,
[I'm replying also to Lukas email because of the similarity]
Stanislav Malyshev wrote:
When you can use string but not object with __toString?
my patch does that
Ok, that's great. So then it makes sense to allow converting int->string
too, right? And then it'd also make sense to allow
Lukas Kahwe Smith wrote:
Suddenly I need to ensure that all my variables have the proper types.
So what will people do? They will start forcing type juggeling manually
before they call the library in question. Since this is the glue code,
its the kind of code you have to write day in day out. S
Hi,
I don't get this deprecation and thus the forced code change at all.
Considering the amount of code using this style, see
http://www.google.com/codesearch?as_q=\%24[a-z][a-z0-9_]*{[^}]%2B}&hl=en&as_lang=php
and given that no PHP code change has been done I would rather suggest
removing the
Since some raised issues with the word "lexical", what do people think to just
re-use the (afaik deprecated) "var" keyword, so we won't need a new keyword in
the chain.
cheers,
- Markus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
Now that it has been deprecated (also looking at
http://wiki.php.net/doc/scratchpad/upgrade/53?s[]=ticks and
http://wiki.php.net/todo/php53?s[]=ticks), I'm wondering whether there's
alternative to this functionality? Or is this completely phased out from PHP
without a replacement?
thank
Hi,
Scott MacVicar wrote:
> It's been removed without a replacement since I don't believe there has
> been a concrete use case given for it.
Probably true, I remember it having used for quite uncommon cases but it was
useful (especially in CLI functions, having to work with signals and such).
Hi,
[CCing interested parties based on the last mail exchange on this topic]
will the deprecation of ticks affect the usage of pcntl_signal? The manual
says [1] "... As of PHP 4.3.0 PCNTL uses ticks as the signal handle callback
mechanism ...". Current practice requires to "declare(ticks = 1);
Hi,
Andrey Hristov wrote:
isn't that easily solved by using a opcode cache?
I think this is also one of the things you won't have often at hosters.
I guess there's a speedup by having one file and no cache available,
which is the argument here. Question is: where does that leave us :) If
I
Hi,
Lukas Kahwe Smith wrote:
That being said I never used this function or the constants in my code.
So is there anyone that does actually use it and has some objection?
Me neither, but in such cases it's probably a good idea to take a look
at code search machines, e.g.
http://www.google.co
Hi,
albeit *not* as a daemon, we've successfully developed a Crawler in PHP
within our company. It can run for hours without a leak, if I remember
correctly it's peak memory consumption is below 64MB. However we're
crawling only a small amount of URLs, just around 10.000 .
As Brian mentioned: fre
Sorry to hijack, but ...
Christopher Jones wrote:
> oci8.events and oci8.old_oci_close_semantics are boolean, so we can
> take this opportunity to change the 1 and 0 to On and Off.
... I've never understood why writing On/Off is a good idea, when it is
not intuitive that the value returned from i
Hi,
the patch is in the bug report ( http://bugs.php.net/bug.php?id=34023 )
or do you meant something else?
thanks,
- Markus
Jani Taskinen wrote:
If the patch was downloadable somewhere, I bet someone had
already committed it. :)
--Jani
On Wed, 14 Dec 2005, Markus Fischer
Steph Fox wrote:
It's been in PAT for ages, unless you made any changes to it Markus?
http://www.zend.com/zend/week/pat/pat52.txt
No change was done. Wow, I didn't knew that this exists. And now it
makes sense because you were mentioned PAT in your email back then which
didn't mean anything
Hi,
Antony Dovgal wrote:
On 25.01.2006 16:17, Markus Fischer wrote:
the patch is in the bug report ( http://bugs.php.net/bug.php?id=34023
) or do you meant something else?
Jani meant that it would be better to put this patch as a downloadable
file (applying copy-pasted patches causes some
John Coggeshall wrote:
Sorry this fell off my radar. Is getParent() a new function to tidy? I
may have to include some lib checks in my config...
I can't tell, http://tidy.sourceforge.net/docs/api/group__Tree.html
lists it and the page was generated in 2002 if that date is correct.
Ob my sys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
[response is at the bottom]
Ilia Alshanetsky wrote:
> Nuno Lopes wrote:
>> In the last days I've exchanged some e-mails with PCRE's author
>> because of one more bug that appeared in our database about segfaults
>> in PCRE (related to stack overf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Jared Williams wrote:
> Replacing the list, with divs and using css generated content to display the
> line numbers, cleans up the paste output but won't get
... and doesn't work in IE. So no real win here. The semantic solution
would be to use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
okay, so with whom I've to sleep to get this patch in? :)
cheers,
- - Markus
Markus Fischer wrote:
> Hi,
>
> Antony Dovgal wrote:
>> On 25.01.2006 16:17, Markus Fischer wrote:
>>> the patch is in the bug report ( h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Zmievski wrote:
> The best Derick and I could come up with is a user-specified conversion
> error handler. It would be invoked only when the converter encounters an
> illegal sequence or other serious error. The existing subst, skip, etc
> error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derick Rethans wrote:
> http://files.derickrethans.nl/pseudoandrei
Ah great, it was just not getting "the point". Sorry for the spam.
- - Markus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just to support your proposal: yes. Even as a long term PHP user I found
exactly this problem some months ago. Since I'm familiar with the PHP
source and usually have a checkout around somewhere I can quickly check
functions and I was lazy not reportin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Burger wrote:
> Ones again E_ALL is for development.
Is this the statement of all developers or only yours?
I have to enable E_ALL on live servers (display_errors to 0), because
whatever resource you have at your hand, you just can't make sure
1 - 100 of 243 matches
Mail list logo
