On Mon, Feb 02, 2004 at 02:09:33AM -0700, Luke Palmer wrote:
: I've been writing a lot of compiler recently, and figuring as how Perl
: 6 is aiming to replace yacc, I think I'll share some of my positive and
: negative experiences. Perhaps Perl 6 can adjust itself to help me out
: a bit. :-)
Pe
On Feb 2, 2004, at 5:20 PM, Larry Wall wrote:
That being said, we can potentially use × U+00D7 MULTIPLICATION SIGN.
(Though my vim can't seem to decide whether it's a single-width or a
double-width character, urgh...)
I realize this is a tad OT, but can anyone tell me how I can get Emacs
to prop
On Mon, Feb 02, 2004 at 11:44:17AM -0700, Luke Palmer wrote:
: Alex Burr writes:
: > --- Andy Wardley <[EMAIL PROTECTED]> wrote:
: >
: > > Adding unicode operators to Perl will just reinforce
: > > its reputation as
: > > a "line noise" language.
: >
: > Perl6, the language with *real* runes.
: >
On Mon, Feb 02, 2004 at 01:14:48PM -0500, John Macdonald wrote:
: On Mon, Feb 02, 2004 at 09:59:50AM +, Simon Cozens wrote:
: > [EMAIL PROTECTED] (Andy Wardley) writes:
: > > Sure, make Perl Unicode compliant, right down to variable and operator
: > > names. But don't make people spend an aft
Alex Burr writes:
> --- Andy Wardley <[EMAIL PROTECTED]> wrote:
>
> > Adding unicode operators to Perl will just reinforce
> > its reputation as
> > a "line noise" language.
>
> Perl6, the language with *real* runes.
>
> Come to think of it, some of the ogham runes would
> look more incharacter
On Mon, Feb 02, 2004 at 09:59:50AM +, Simon Cozens wrote:
> [EMAIL PROTECTED] (Andy Wardley) writes:
> > Sure, make Perl Unicode compliant, right down to variable and operator
> > names. But don't make people spend an afternoon messing around with mutt,
> > vim, emacs and all the other tools
--- Andy Wardley <[EMAIL PROTECTED]> wrote:
> Adding unicode operators to Perl will just reinforce
> its reputation as
> a "line noise" language.
Perl6, the language with *real* runes.
Come to think of it, some of the ogham runes would
look more incharacter as a 'distribute' operator than
guill
Luke Palmer wrote:
> I think $() will help somewhat, as will interpolating method calls, but
> for a compiler, I'd really like PHP-like parse switching. That is, I
> could do something like (I'll use $< and $> for ):
Check out the new scanner module for Template Toolkit v3. It does this
exactly
[EMAIL PROTECTED] (Andy Wardley) writes:
> Sure, make Perl Unicode compliant, right down to variable and operator
> names. But don't make people spend an afternoon messing around with mutt,
> vim, emacs and all the other tools they use, just so that they can read,
> write, email and print Perl
I've been writing a lot of compiler recently, and figuring as how Perl
6 is aiming to replace yacc, I think I'll share some of my positive and
negative experiences. Perhaps Perl 6 can adjust itself to help me out
a bit. :-)
=over
=item * RegCounter
I have a class called RegCounter which is of
Luke Palmer wrote:
> But I'm still sure that the unicode-deficient would rather write:
I suspect the unicode-deficient would rather write Ruby.
Adding unicode operators to Perl will just reinforce its reputation as
a "line noise" language.
I know it has been said before, and I'm sure it will be
11 matches
Mail list logo
