Mail problems? [simon@cozens.net: Re: Now, to try again...]

[Simon Cozens]

This is the fourth time I've sent this mail to perl6-internals-api-parser,
but it doesn't seem to be arriving. None of my other mail is affected, and
perl5-porters is, for once, behaving itself; why this list in particular? 

- Forwarded message from Simon Cozens <[EMAIL PROTECTED]> -

Damn this is annoying. Is it perl.org that's dropping mail or me?

- Forwarded message from Simon Cozens <[EMAIL PROTECTED]> -
On Sat, Dec 16, 2000 at 08:09:23PM +, David Grove wrote:
> Thinking of just the parser as a single entity seems to me to be headed into
> trouble unless we can define in advance what type of role these dialects
> will play in the language, and at what point they merge into a single entity
> and how.

I can understand each word in this sentence, but put together they don't
appear to make much sense.

I think you're getting needlessly hung up on this idea of "dialects", whatever
you seem to believe they are. We're not parsing dialects, we're parsing
*COMPLETELY DIFFERENT THINGS*. 

Python is not a dialect of Perl. 

There are a number of ways we could do this. We could allow the user to use
source filters to turn Python into Perl, which is what happens currently, with
some success. We could allow the user to write their own parser and turn
Python into an op tree, which allows much greater flexibility. Or, we could
allow the user to override parts of the parser's operation, allowing for ease
of modification. Or all three.

> (or worse, multiple "parser/lexer/tokenizer single-entity parts"...
> meaning redundant duplication of extra effort over and over again
> repeatedly).

Huh? I'm just thinking of a system of callbacks. You can overload operators in
Perl, and while this is slightly confusing, it isn't earth-shattering. Now,
I'm hoping that you'll be able to overload parser operations in Perl 6.

- End forwarded message -
-- 
>Almost any animal is capable learning a stimulus/response association,
>given enough repetition.
Experimental observation suggests that this isn't true if double-clicking
is involved. - Lionel, Malcolm Ray, asr.

- End forwarded message -
-- 
Sigh.  I like to think it's just the Linux people who want to be on
the "leading edge" so bad they walk right off the precipice.
(Craig E. Groeschel)

Re: Mail problems? [simon@cozens.net: Re: Now, to try again...]

[Ask Bjoern Hansen]

On Sun, 17 Dec 2000, Simon Cozens wrote:

> This is the fourth time I've sent this mail to perl6-internals-api-parser,

I've seen it on the list at least twice.

> but it doesn't seem to be arriving. None of my other mail is affected, and
> perl5-porters is, for once, behaving itself; why this list in particular? 

Send me the log snippets from your mailserver successfully
delivering the mail to one of the perl.org mx'es and I can look
after it.

If it was before the weekend, don't bother though. The 70MB's I have
for qmail logs rotate pretty quickly.

So maybe this is better: Next time you think it happens, send me a
mail right away and I can look into it.

(perl.org haven't ever dropped mail since I started taking care of
it as far as I know. Are you sure that you'll receive bounces, your
envelope sender is often changing).


 - ask
 
-- 
ask bjoern hansen - 
more than 70M impressions per day,