I think we should rename flex to something else because you just
confused me with that new Adobe not-quite-flash flex thingie...
:-) :-) ;-)
Just Kidding!!!
(Not about the confusing me part, as we all know that's trivial...)
On Mon, August 20, 2007 5:04 am, Marcus Boerger wrote:
> Hello Gregory
Hello Gregory,
the good news on this fron is that re2c meanwhile has a new beta version
with flex like conditoin support. Also when changing from flex to re2c we
should switch from bison to lemon. All in all a damn huge amount of work.
But the result would be much cleaner, faster, more flexible,
Ralph Schindler wrote:
> Hey David & Lucas,
> I brought this up a year ago on the list here:
>
> http://marc.info/?t=11472819373&r=1&w=2
>
> Essentially, the trend will continue to be that as keyword requiring
> features are added, the global naming space will continue to become
> smaller a
Hey David & Lucas,
I brought this up a year ago on the list here:
http://marc.info/?t=11472819373&r=1&w=2
Essentially, the trend will continue to be that as keyword requiring
features are added, the global naming space will continue to become
smaller and less safe for older applications
On 8/16/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Nicolas,
>
> yes. All my global functions and my classes are prefixed.
Prefix the methods are not a solution.
The only cases where it is acceptable are the magic methods (when we
introduce new ones) like __get/set. But that happens r
I wasn't talking about global functions and classes, I was talking about
class methods. David pretty much sums this up in his email.
On 8/16/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>
> Hello Nicolas,
>
> yes. All my global functions and my classes are prefixed.
>
> marcus
>
> Thursday, Aug
On 8/16/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Lukas,
>
> this is a no issue. Prefix your code and be done!
>
That means prefixing your methods as well ?
The problem is when one calls something like a method "import()"
You prefix your functions ? I think this is silly. Prefix th
Hello Nicolas,
yes. All my global functions and my classes are prefixed.
marcus
Thursday, August 16, 2007, 10:37:30 PM, you wrote:
> In that specific case, a method called import() was in cause (of course,
> conflicting with the namespace/package/whatever package). Do you propose
> prefixing
In that specific case, a method called import() was in cause (of course,
conflicting with the namespace/package/whatever package). Do you propose
prefixing all method names ?
On 8/16/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
>
> Hello Lukas,
>
> this is a no issue. Prefix your code and be do
Hello Lukas,
this is a no issue. Prefix your code and be done!
marcus
Wednesday, August 15, 2007, 3:37:20 PM, you 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 g
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
>> 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
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
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
16 matches
Mail list logo
