Thanks for another great argument to move away from PHP asap.
On 25.10.2008, at 20:07, Lukas Kahwe Smith wrote:
that we have decided to go with backslash as new separator for
namespaces.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.p
+1 for #3 ("use namespace" or "use class")
Regards,
Benjamin
On 15.10.2008, at 22:35, Greg Beaver wrote:
Hi,
http://wiki.php.net/rfc/namespaceissues
Read it and discuss. Let's be clear people: the technical problems in
namespaces are limited and solvable. The problems in the political
envi
Hi
This commit is responsible for the bad performance:
http://cvs.php.net/viewvc.cgi/php-src/configure.in?r1=1.579.2.52.2.77.2.11&r2=1.579.2.52.2.77.2.12&diff_format=u
-gstabs versus -g should have no effect on production performance.
Ok, maybe i made a mistake, that's what i compared:
ben
Hi,
On 31.03.2008, at 11:37, Stefan Esser wrote:
I just want to bring attention to the fact that while benchmarks show
that PHP 5.3 is faster than PHP 5.2 on linux systems on MacOS/X the
opposite is shown.
Actually just executing bench.php from the PHP distribution shows that
PHP 5.3 is about h
On 28.03.2008, at 13:22, Lars Strojny wrote:
The issue I have with ArrayAccess is, that an archive
represents a multidimensional, nested hash. The way Phar works as an
array is doubtful as it represents multi dimensions in a single
dimension hash.
Very good point!
On 28.03.2008, at 13:22, Lar
Hi Marcus,
First thing: yes i fully understand what the code is doing but i
still
think that it doesn't need to be so "hackish".
I wouldn't call it hackish. I'd eventually call it new to people that
haven't used the new PHP 5.0 features yet.
I used PHP 5 when it had namespaces the first ti
Hi,
i just read the phar examples in the manual and found things like this:
$p = new Phar('coollibrary.phar');
if (Phar::canWrite()) {
$fp = fopen('hugefile.dat', 'rb');
$p['data/hugefile.dat'] = $fp;
if (Phar::canCompress()) {
$p['data/hugefile.dat']->setCompressedGZ();
}
On 05.12.2007, at 17:43, Sebastian Bergmann wrote:
Matthias Pigulla schrieb:
Given that it was technically feasible, (future) core classes should
be in namespaces as well.
Or
- Introduce namespaces in PHP 6
- Move all functions and classes that are now global into
(per-extension) names
On 05.12.2007, at 04:28, Steph Fox wrote:
I'd like wildcard support too... and support for multiple namespaces
per file (for bundling only)... but neither of those are complete
deal-breakers in my eyes. Protection from naming collisions, is.
FULLACK, the good news is that i accidently mail
Hi,
What about __class_exists() and SPL_register_class_exists_handler()?
One could suppose the classloader (the one that implements
__autoload) knows if a class exists (as in: is registered within the
classloader or the class-file exists) without loading it and maybe
the class that calls c
The exception example is well an exception. Here you must inherit
exception.
That is simply how PHP works, it is an intended limitation. That
said in
this case you should not use Exception for your own stuff. Name it
after
your library or product, like MyProductException.
Hey, i have an
The above code works just fine.
Yes there is a concept. import is best used within a namespace. So,
namespace your code and there is no need to import global classes.
Yep, it works if your whole application uses one namespace, but what
if you have a core package that defines some except
if your exception is so general that it is called exception you can
obviously simply use exception.
Maybe _my_ exception is a generic exception in _my_ framework and
implements some helper functions i need? But the discussion is not
about exceptions, it's about classnames that PHP declare
On 02.10.2007, at 22:04, Stanislav Malyshev wrote:
I wouldn't actually recommend using such code. If you have
Foo::Exception just use Foo::Exception - it's short enough :)
And what if not? "throw App::package::subpackage::Exception" in a
file that has the namespace "App::package::su
Hi all,
import Foo::Bar AS DomDocument;
import Foo::Exception;
import MyStuff::Dom::XsltProcessor;
Result in a "Fatal error: Import name '...' conflicts with defined
class"
Of course i want to refer to my own exception in my application or
framework as "Exception", and of course i want to us
Hi Wez,
this patch that adds a msg_queue_exists() to ext/sysvmsg. Currently
there is no way to tell wether msg_get_queue() will create or just a
attach to a queue.
It would be great to see this function in the next PHP release.
Benjamin
diff -u php-5.2.1/ext/sysvmsg/php_sysvmsg.h
php-5.2.1
16 matches
Mail list logo
