Stanislav Malyshev schrieb:
> I wonder why everybody here talks about one and only one language -
> Java.
Java just happens to be the programming language that I associate the
most with the programming language feature in question.
--
Sebastian Bergmann http://sebastia
Could you give definition of what is a package, so we could see if it
resembles more of a package or less?
http://java.sun.com/docs/books/jls/second_edition/html/packages.doc.html
I wonder why everybody here talks about one and only one language -
Java... It's not like programming languages
Stanislav Malyshev schrieb:
> Could you give definition of what is a package, so we could see if it
> resembles more of a package or less?
http://java.sun.com/docs/books/jls/second_edition/html/packages.doc.html
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG
At least, I have one additional namespace related patch, that is not
accepted yet.
Renaming may require a lot of additional work with it.
Also, I am not sure that allbody agree with "package".
Thanks. Dmitry.
> -Original Message-
> From: Derick Rethans [mailto:[EMAIL PROTECTED]
> Sent:
On Wednesday 15 August 2007, Stanislav Malyshev wrote:
> > If PHP team release in the news:
> >
> > PHP has namespace support!
> > OR
> > PHP has package support!
> >
> > Everyone will understand what does that mean. Those that do not
>
> I wouldn't. And that's not because I'm so dense, but because
Per previous discussion on internals, there are other "more active"
maintainers for COM right now, and by assigning to me, you're
assigning to the wrong person.
If you don't care, that's fine, it's just that "assigned" is not
really the correct disposition for the ticket in that case; bette
This leaves the "Namespace" name available for future development if/as
Which means we officially declare PHP *doesn't* have namespaces (since
we reserve the right to develop it in the future, it's obvious we didn't
do it yet). Why it would be a good thing?
needed (such as if the language w
On Aug 15, 2007, at 2:00 PM, Christopher Jones wrote:
Did you get any further with merging this? It would help users of
the XQuery language.
If I understand your intent, I would be able to change the code
fragment
below to use a nowdoc, and not have to escape the XQuery $i variables.
Chris
> That's not true. Even if you discount people that don't care or dare
> enough to write on the list, there were still people who wrote in
> support of keeping "namespace" and they weren't me :)
Okay, I'll dare.
I vote for using the name "Package" for the current implementation.
This leaves the
A software package is that beautiful box you go to the supermarket and
buy the product. A package in programming language is exactly what I
wrote to you.
If by programming language you mean Java, since some people consider
these to be synonymous ;)
No. You mentioned not only once that namesp
On 8/15/07, Guilherme Blanco <[EMAIL PROTECTED]> wrote:
> On 8/15/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > > Take a look at this URL and tell me which one PHP does look like:
> > > http://kaistizen.net/Project/CSharpJava/csharp_java.htm#NamespaceVsPackage
> >
> > Neither, actually. But
On 8/15/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > Take a look at this URL and tell me which one PHP does look like:
> > http://kaistizen.net/Project/CSharpJava/csharp_java.htm#NamespaceVsPackage
>
> Neither, actually. But it's not about "should we imitate C# or Java".
> It's about what'
Take a look at this URL and tell me which one PHP does look like:
http://kaistizen.net/Project/CSharpJava/csharp_java.htm#NamespaceVsPackage
Neither, actually. But it's not about "should we imitate C# or Java".
It's about what's best for PHP. My opinion is that for PHP would be best
to have na
On 8/15/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > current implementation doesn't have braces; this (consequently) adds a
>
> Ouch, not braces again. What is it with braces that you need them so
> badly? Many languages aren't using the things ever, isn't it a proof
> that there's life o
On 8/15/07, Marc Gear <[EMAIL PROTECTED]> wrote:
> On 8/15/07, Guilherme Blanco <[EMAIL PROTECTED]> wrote:
> > > ZF is using Very_Very_Long_And_Very_Irritating_Class_Names because
> > > there's no choice to do otherwise.
> > If you are creating this patch only to simplify this, I recommend you
> >
On 8/15/07, Guilherme Blanco <[EMAIL PROTECTED]> wrote:
> > ZF is using Very_Very_Long_And_Very_Irritating_Class_Names because
> > there's no choice to do otherwise.
> If you are creating this patch only to simplify this, I recommend you
> to keep it as PHP is currently and just add namespace/packa
Hannes Magnusson wrote:
On 8/15/07, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
Hi,
Someone in the Doctrine channel just brought up the issue of having to
look forward to ensure mid term compatibility when choosing names for
identifiers. I guess with namespaces and other things will add new
re
Stanislav Malyshev wrote:
Wikipedia also define the term MVC. But alas, that is a conceptual
definition, not blueprints for implementation.
Who cares about the implementation? It's still MVC. So let's implement
MVC and call it "distributed enterprise messaging" and then let's spend
next 2 ye
On 8/15/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> > PHP has namespaced package support.
>
> Yep, that's what I was talking about. "We have namespaces but we call it
> packages because Java does". Eek.
>
Take a look at this URL and tell me which one PHP does look like:
http://kaistizen.ne
I have no serious objections about renaming. I am asking to wait a bit.
If you think "package" is fine, why wait with renaming it?
Because there are others that don't think name "package" is better?
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)25
PHP has namespaced package support.
Yep, that's what I was talking about. "We have namespaces but we call it
packages because Java does". Eek.
Wikipedia also define the term MVC. But alas, that is a conceptual
definition, not blueprints for implementation.
Who cares about the implementati
Stanislav Malyshev wrote:
If PHP team release in the news:
PHP has namespace support!
OR
PHP has package support!
PHP has namespaced package support.
Which, is what the implementation is.
Or worked with different ones enough to understand that "packages" is
used for a zillion of different t
On Fri, 10 Aug 2007, Dmitry Stogov wrote:
> I have no serious objections about renaming. I am asking to wait a bit.
If you think "package" is fine, why wait with renaming it?
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP R
If PHP team release in the news:
PHP has namespace support!
OR
PHP has package support!
Everyone will understand what does that mean. Those that do not
I wouldn't. And that's not because I'm so dense, but because "package"
could mean anything, from next generation autoloader (I myself propose
Stan,
Sorry to disappoint you, but your idea is wrong.
If PHP team release in the news:
PHP has namespace support!
OR
PHP has package support!
Everyone will understand what does that mean. Those that do not
understand are the ones that had never worked with it and can work in
the future (and wi
It's not about the popularity of a word, but the meaning of it. If it
resembles more of a package, let's call it package (as it does
Could you give definition of what is a package, so we could see if it
resembles more of a package or less?
currently, namespace should be nested.. but that's m
On 8/15/07, Olivier Hill <[EMAIL PROTECTED]> wrote:
> It's not about the popularity of a word, but the meaning of it.
A package means a collection of related classes and thats not whats
happening- it is a scoping level for a particular file. A namespace
is a scope which groups related identifiers
Marc,
This is not the right reason for naming it namespace.
Example:
Say I am writing a new language. I want to introduce something similar
to functions. But since OO is popular and sounds nice.. why not call
it method on an object?
People are asking for objects.. I'll just give them objects.
Hi all
Attached* is a patch introducing a new parameter to in_array() and
array_search() which will set the internal pointer to the first
location of $needle in the $haystack (granted that $needle exists
within the $haystack).
This will make it possible to search for a value in an array and then
>> Someone in the Doctrine channel just brought up the issue of having to
>> look forward to ensure mid term compatibility when choosing names for
>> identifiers. I guess with namespaces and other things will add new
>> reserved words. I think we should have a prominent place on php.net with
>> ear
On 8/15/07, Alain Williams <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 15, 2007 at 03:37:20PM +0200, Lukas Kahwe Smith wrote:
> > Hi,
> >
> > Someone in the Doctrine channel just brought up the issue of having to
> > look forward to ensure mid term compatibility when choosing names for
> > identifiers
On 8/15/07, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Someone in the Doctrine channel just brought up the issue of having to
> look forward to ensure mid term compatibility when choosing names for
> identifiers. I guess with namespaces and other things will add new
> reserved words. I
FWIW I am for "namespaces" because:
- the functionality mentioned most often as missing in PHP is
'namespaces'. People want 'namespaces' (see
http://en.wikipedia.org/wiki/PHP#Criticism)
- What they really want is no more clashing
classes/functions/variables when they integrate third party apps
(wh
On Wed, Aug 15, 2007 at 03:37:20PM +0200, Lukas Kahwe Smith wrote:
> Hi,
>
> Someone in the Doctrine channel just brought up the issue of having to
> look forward to ensure mid term compatibility when choosing names for
> identifiers. I guess with namespaces and other things will add new
> rese
On 15.08.2007 17:13, Christian Speich wrote:
hello,
I think the code should look like this:
if (defined(__APPLE__) || defined(__APPLE_CC__)) && (defined
(__BIG_ENDIAN__) || defined(__LITTLE_ENDIAN__))
# if defined(__LITTLE_ENDIAN__)
# undef WORDS_BIGENDIAN
# else if defined(__BIG_ENDIAN__)
Hi,
Someone in the Doctrine channel just brought up the issue of having to
look forward to ensure mid term compatibility when choosing names for
identifiers. I guess with namespaces and other things will add new
reserved words. I think we should have a prominent place on php.net with
early wa
hello,
I think the code should look like this:
if (defined(__APPLE__) || defined(__APPLE_CC__)) && (defined
(__BIG_ENDIAN__) || defined(__LITTLE_ENDIAN__))
# if defined(__LITTLE_ENDIAN__)
# undef WORDS_BIGENDIAN
# else if defined(__BIG_ENDIAN__)
# define WORDS_BIGENDIAN
# endif
#endif
Yes
37 matches
Mail list logo
