[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FYI: support for partial messages (i.e. chained diagnostics)
From: |
Akim Demaille |
Subject: |
Re: FYI: support for partial messages (i.e. chained diagnostics) |
Date: |
09 Oct 2002 08:17:18 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
[Resent]
| >>> "Akim" == Akim Demaille <address@hidden> writes:
| Akim> how about having `msg' and the like return an object
| Akim> message, and have a means to extend a message object?
|
| Akim> my $msg = new msg;
| Akim> $msg->msg 'channel', 'foo:3', 'redefinition of A ...';
| Akim> $msg->msg 'channel', 'foo:1', '... A previously defined here';
|
| Akim> Which would be equivalent to (but nicer than):
|
| Akim> my $msg = msg 'channel', 'foo:3', 'redefinition of A ...';
| Akim> $msg->msg 'channel', 'foo:1', '... A previously defined here';
|
| In both cases, you also need a way to indicate when the message
| is terminated and should be sent. E.g. $msg->finish.
Hm... It was my understanding that things were buffered? Then there
is no need for `finish' AFAICT.
| I agree we could have message objects _in addition_ to the present
| `msg' function. As you say this would avoid the $partial buffer.
| But IMO that requires some additional machinery we don't need at the
| moment.
Agreed.