I don't think this part is a concern since we have required re2c for
quite a while now to build many critical parts of PHP. People who
Ok, great then - only issue remaining is the multibyte support.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)2
Hi!
Were the stream support issues solved?
We completely dropped multibyte support. The reason is that the way we were
I wasn't asking about multibyte (that we discuss below), but about other
streams - I think I mentioned it on IRC last time re2c parser was
discussed. I remember re2c used
https://re2c.svn.sourceforge.net/svnroot/re2c/trunk/re2c
[6] http://php.net/~helly/php-re2c-20080302.diff.txt
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello Rasmus,
Monday, March 3, 2008, 12:25:52 AM, you wrote:
> Stanislav Malyshev wrote:
>> Hi!
>>
>>> be much easier, switching to re2c promises a much faster lexer.
>>> Actually,
>>> without any specific re2c optimizations we already get around a 20%
>>> scanner
>>
>> I think 20% faster is ve
Hi Stan,
On Sun, Mar 2, 2008 at 11:47 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Hi!
>
>
> > be much easier, switching to re2c promises a much faster lexer. Actually,
> > without any specific re2c optimizations we already get around a 20% scanner
>
> I think 20% faster is very cool.
>
Hello Stanislav,
Sunday, March 2, 2008, 11:47:57 PM, you wrote:
> Hi!
>> be much easier, switching to re2c promises a much faster lexer. Actually,
>> without any specific re2c optimizations we already get around a 20% scanner
> I think 20% faster is very cool.
> However, as I understand re2c is
Stanislav Malyshev wrote:
Hi!
be much easier, switching to re2c promises a much faster lexer.
Actually,
without any specific re2c optimizations we already get around a 20%
scanner
I think 20% faster is very cool.
However, as I understand re2c is not a standard tool found everywhere.
So what
Hi!
be much easier, switching to re2c promises a much faster lexer. Actually,
without any specific re2c optimizations we already get around a 20% scanner
I think 20% faster is very cool.
However, as I understand re2c is not a standard tool found everywhere.
So what happens if you wanted to us
2c
[4] http://trac.macvicar.net/php-re2c/
[5] https://re2c.svn.sourceforge.net/svnroot/re2c/trunk/re2c
[6] http://php.net/~helly/php-re2c-20080302.diff.txt
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Marcus Boerger wrote:
Hello Pierre,
Saturday, March 1, 2008, 8:53:26 PM, you wrote:
and yeas after several years of trying to communicate and never gotten
anything back? I have told PREAR development a million times to fix code.
Now not even PEAR code is wrong but it is copied into endless amou
feel free to delete all mail from me today
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
really sorry... qmail is nasty
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
maybe the last...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
another test. ignore me!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
please ignore
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Joshua,
seams to me the interest in traits decreases rapidly :(
Joshua Thompson schrieb:
trait A1 {
private $a = 'A1';
private function printA() {
echo $this->a;
}
public function callPrintA1() {
$this->printA();
}
}
trait A2 {
private $a = 'A2';
16 matches
Mail list logo
