Stanislav Malyshev wrote:
>> namespace Foo;
>> import Exception;
>
> Once more, import with one-term argument is a no-op. And will stay so.
> That's why we have the warning.
>
>> I think that either import ::Exception needs to work, or import
>> Exception shouldn't issue a warning.
>
> We'll discus
namespace Foo;
import Exception;
Once more, import with one-term argument is a no-op. And will stay so.
That's why we have the warning.
I think that either import ::Exception needs to work, or import
Exception shouldn't issue a warning.
We'll discuss this one. I wonder if anybody else feel
Quoting Stanislav Malyshev <[EMAIL PROTECTED]>:
Yes. I think that if you use an unqualified name it should always
be relative to the namespace (and importing internal classes into
your namespace lets you use short names for them, avoiding
::Exception).
Unfortunately, there are problems wi
Quoting Stanislav Malyshev <[EMAIL PROTECTED]>:
import Exception;
-> name conflict, which seems correct
import Exception is a no-op, so I don't understand how you could
have got name conflict. Do you mean "import Test::Exception"? That
should work, if it didn't it's a bug.
It turns out t
Stanislav Malyshev wrote:
>> Hold off for a bit - I may have a simple solution that solves the
>> problem for class names, method names and functions, have to code the
>> patch tonight first to prove it works.
>
> OK, please send it as soon as you have it :)
Hi,
The attached patch is for PHP 5.3,
Marcus Boerger wrote:
> Hello Gregory,
>
> even if you can solve it easily your patch will not solve the fact that we
> won't have a token for that keyword the, or am i missing something?
>
> marcus
Hi Marcus,
Just finished the patch (see separate reply), and in my tests, the
keyword still wor
Stanislav Malyshev wrote:
Since many packages (wordpress, propel, horde, phing, etc.) use "import"
as either class or function name, and we couldn't find a good solution
to make it work with import keyword without going into all kinds of
troublesome hacks, so we are thinking about replacing 'im
Yes. I think that if you use an unqualified name it should always be
relative to the namespace (and importing internal classes into your
namespace lets you use short names for them, avoiding ::Exception).
Unfortunately, there are problems with this solution, since it
makes common case harder to
Hold off for a bit - I may have a simple solution that solves the
problem for class names, method names and functions, have to code the
patch tonight first to prove it works.
OK, please send it as soon as you have it :)
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://ww
Hello Gregory,
even if you can solve it easily your patch will not solve the fact that we
won't have a token for that keyword the, or am i missing something?
marcus
Tuesday, October 23, 2007, 1:18:52 AM, you wrote:
> Stanislav Malyshev wrote:
>> Hi all!
>>
>> Since many packages (wordpress
Stanislav Malyshev wrote:
> Hi all!
>
> Since many packages (wordpress, propel, horde, phing, etc.) use "import"
> as either class or function name, and we couldn't find a good solution
> to make it work with import keyword without going into all kinds of
> troublesome hacks, so we are thinking ab
Your message dated Mon, 22 Oct 2007 15:41:37 -0700 with subject "Returned
mail: see transcript for details" has been submitted to the moderator of the
TOURBUS list: =?UTF-8?Q?Bob_Rankin?= <[EMAIL PROTECTED]>.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:/
Hi all!
Since many packages (wordpress, propel, horde, phing, etc.) use "import"
as either class or function name, and we couldn't find a good solution
to make it work with import keyword without going into all kinds of
troublesome hacks, so we are thinking about replacing 'import' keyword
wi
Ahh, I see, that's a bit disappointing. Any reason why it doesn't/shouldn't
work ?
Yes. Test::Foo is a class name, so you can't make part of it variable
and part not, just as you couldn't write:
$var = "bar";
$a = new foo$var();
and expect new instance of class "foobar". You'd have to compos
On Sunday 21 October 2007, Stanislav Malyshev wrote:
> > Using dynamic class names works fine without namespaces, but
> > doesn't work at all with namespaces. Take this simple example:
> >
> > > namespace test;
> > class Foo {}
> > $class = "Foo";
> > $foo = new test::$class();
> > ?>
> >
> > Wi
On 22.10.2007, at 17:31, Marcus Boerger wrote:
Hello Lukas,
I think all pecl modules should follow the core rules and that means
CODINT_STYLE should apply to pecl as much as it does to core. We
should
hence provide an easy to read (as in html or pdf or whatever)
version that
is accessible
Hello Lukas,
I think all pecl modules should follow the core rules and that means
CODINT_STYLE should apply to pecl as much as it does to core. We should
hence provide an easy to read (as in html or pdf or whatever) version that
is accessible online easier and in a more prominent space than the c
The following is just an opinion from an user and should be considered as
such.
You should consider that the PEAR way of naming classes was the nasty
workaround that the namespaces is trying to solve. Therefore, just trying to
make the language fit your needs so you can still use that nasty workar
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (60 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
===
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (628 total including feature requests)
===[*Programming Data Structures]=
40496 Assigned Test bug35239.phpt still fails (works in PHP 5)
=
Hi,
I've already opened a feature request (#43048) but I feel, that there
need to be a discussion on that topic. The problem is, that the current
pseudo-namespacing used by a huge number of projects (PEAR-style, with
underscores and the related file organisation), could not be easily
ported to nam
21 matches
Mail list logo
