Hi,
I like this idea very much, too but I do see the problems in doing it
correctly.
From my point of view the problem looks as follows:
PHP arrays are a wonderful universal construct but it is problematic
to use them in scenarios where you dont want to bind directly to the
single, avail
Hi,
On Jun 30, 2009, at 7:31 PM, Rasmus Lerdorf wrote:
Roman Borschel wrote:
Some new 5.3 features like closures and the :? operator still cause
bus
errors with APC though. For the former there is already an open
ticket
since february. So I dont think APC is really 5.3 compatible yet
but
Some new 5.3 features like closures and the :? operator still cause
bus errors with APC though. For the former there is already an open
ticket since february. So I dont think APC is really 5.3 compatible
yet but I'm sure it wont take long until these issues are fixed now
that 5.3 is out.
Hi,
i created 2 patches that are attached to this mail, one to fix the
issue and the other to add tests for it (I added them into
reflectionProperty_setAccessible.phpt).
Roman
On Apr 4, 2009, at 1:23 PM, Johannes Schlüter wrote:
On Sat, 2009-04-04 at 13:08 +0200, Roman Borschel
s appreciated.
Roman
On Apr 4, 2009, at 9:02 AM, Roman Borschel wrote:
For what it matters, the same thing in Java returns the expected
result:
Class clazz = Foo.class;
Field fooProp = clazz.getDeclaredField("foo");
fooProp.setAccessible(true);
Bar bar = new Bar();
String value = (String
some weird behavior I just don't understand yet?
Roman
On Apr 4, 2009, at 7:34 AM, Roman Borschel wrote:
Hi,
On Apr 4, 2009, at 1:53 AM, Johannes Schlüter wrote:
On Fri, 2009-04-03 at 22:37 +0200, Roman Borschel wrote:
Given the following simple classes
class Foo {
private $foo = &#x
Hi,
On Apr 4, 2009, at 1:53 AM, Johannes Schlüter wrote:
On Fri, 2009-04-03 at 22:37 +0200, Roman Borschel wrote:
Given the following simple classes
class Foo {
private $foo = 'value';
public function getFoo() { return $this->foo; }
}
class Bar extends Foo {}
Obviou
Hi,
i've got a little question that involves private properties,
inheritance and Reflection with PHP 5.3 RC1.
Given the following simple classes
class Foo {
private $foo = 'value';
public function getFoo() { return $this->foo; }
}
class Bar extends Foo {}
Obviously, given an instanc
On Jan 21, 2009, at 4:20 PM, Christian Schneider wrote:
Nathan Rixham wrote:
seems to me that many of the new requests coming in, including my own
stupid ones are because people want to build fast decent orm's in
php -
Having built an ORM system myself I can say that you don't need
Reflecti
Hi,
On Sep 8, 2008, at 8:45 PM, Lukas Kahwe Smith wrote:
On 08.09.2008, at 19:53, Dmitry Stogov wrote:
The main PHP namespaces ideas come from Java packages and Java
classes
have to write these "use" statements in the same way. It's not the
end
of the world. I believe that well-designed
Great work!
+1 from me for your proposals, too!
Roman
On Dec 7, 2007, at 2:36 AM, Gregory Beaver wrote:
Hi Derick,
I've been thinking a *lot* about your provocative email in the past
couple of days, and have come to a different conclusion from my
original
reply (which, as a reminder state
Begin forwarded message:
From: Roman Borschel <[EMAIL PROTECTED]>
Date: December 6, 2007 7:29:19 PM GMT+01:00
To: <[EMAIL PROTECTED]>
Subject: Re: [PHP-DEV] Namespace
Thats true, however frameworks tend to have a lot of different
"namespaces". Just take a look at the Z
On Dec 6, 2007, at 7:08 PM, Michael McGlothlin wrote:
PHP already has the bad habit for many programmers to write totally
unreadable code. It's darn near as bad as Perl in that area. No
reason to make it worse.
And you really think not allowing multiple namespaces in a file will
improve
I don't agree with that. I think multiple namespaces per file would be
fine with the current syntax as this is a feature that would not be
used by that many people and if it's used it's not for development
purposes (who wants to read a class bundle with no comments,
linebreaks etc.?) and th
On Dec 4, 2007, at 6:00 PM, Martin Alterisio wrote:
2) I was under the impression namespaces were introduced to improve
code
maintainability. Was I wrong?
You are right. On the flip side, if you can't use your maintainable
code because it is slow as molasses, that is a problem.
If that's
Yes, thanks i already changed that. Doesnt make a big difference though.
Roman
On Dec 4, 2007, at 6:10 PM, Gergely Hodicska wrote:
vserver. And the xdebug profiling result shows me in fact that this
additional time seems to be spend in the autoload facility and its
require_once calls.
OFF:
On Dec 4, 2007, at 5:50 PM, Martin Alterisio wrote:
2007/12/4, Roman Borschel <[EMAIL PROTECTED]>:
On Dec 4, 2007, at 5:09 PM, Martin Alterisio wrote:
1) Why is performance relevant to whether namespaces are implemented
one per
file or many per file?
Because including/requiring 80
Begin forwarded message:
From: Roman Borschel <[EMAIL PROTECTED]>
Date: December 4, 2007 5:19:54 PM GMT+01:00
To: "Martin Alterisio" <[EMAIL PROTECTED]>
Subject: Re: [PHP-DEV] ignored patches
On Dec 4, 2007, at 5:09 PM, Martin Alterisio wrote:
Sorry to step in uninvi
On Dec 4, 2007, at 5:14 PM, Gregory Beaver wrote:
On the other hand, combining multiple files into a single file results
in line numbers no longer corresponding to the original line numbers
of
the file, adding another translation step when debugging a problem.
Of
course, this is just simpl
, 2007, at 10:48 AM, Roman Borschel wrote:
Hi everyone,
i just want to throw in my 2 cents. I've experimented alot with file
bundling in the past on several projects and i can confirm that is
does have a positive affect in applications that include/require a
lot of files during a reques
Hi everyone,
i just want to throw in my 2 cents. I've experimented alot with file
bundling in the past on several projects and i can confirm that is
does have a positive affect in applications that include/require a lot
of files during a request (at least thats how it looks like!). Yes my
21 matches
Mail list logo
