From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Group based gnus-summary-line-format ?
Date: 16 Mar 1998 04:28:39 +0100 [thread overview]
Message-ID: <kigsoojtiu0.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stainless Steel Rat's message of "15 Mar 1998 22:23:56 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:
>
> Hrvoje> Unless I am missing something obvious, why is the byte-compiler
> Hrvoje> needed at all? It is not hard to imagine code that would keep an
> Hrvoje> alist of the byte-compiled formats and look up the appropriate
> Hrvoje> element. The whole alist could be saved to `.newsrc.eld'.
>
> Because it is hypothetically possible to have a different value for
> gnus-summary-line-format for every group.
In that hypothetical case you will end up having a large cache. What
is your point?
> And unless I am missing something obvious, why is it "bad" to invoke
> the byte-compiler
I've never said it was bad to invoke the byte-compiler, but I did
imply that the code should be designed so that its invocation is not
mandatory.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Psychos _do not_ explode when sunlight hits them."
next prev parent reply other threads:[~1998-03-16 3:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-15 12:09 jari.aalto
1998-03-15 19:56 ` Kai Grossjohann
1998-03-15 21:05 ` jari.aalto
[not found] ` <x7en03qte0.fsf@peorth.gweep.net>
1998-03-16 2:18 ` Hrvoje Niksic
[not found] ` <x7u38zpe1b.fsf@peorth.gweep.net>
1998-03-16 2:54 ` Hrvoje Niksic
[not found] ` <x7ra43pbcj.fsf@peorth.gweep.net>
1998-03-16 3:28 ` Hrvoje Niksic [this message]
[not found] ` <x7u38z2slw.fsf@peorth.gweep.net>
1998-03-16 4:15 ` Hrvoje Niksic
1998-03-16 13:07 ` jari.aalto
1998-03-16 23:42 ` Raja R Harinath
1998-03-19 13:06 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kigsoojtiu0.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).