Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE>
Cc: ding@gnus.org
Subject: Re: Pterodactyl Gnus v0.39 is released
Date: 26 Oct 1998 09:07:08 +0100	[thread overview]
Message-ID: <vafr9vvu4pf.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Hrvoje Niksic's message of "26 Oct 1998 00:59:04 +0100"

>>>>> Hrvoje Niksic <hniksic@srce.hr> writes:

  > But these things are not the point.  The point is that the crucial
  > difference (IMHO) is whether the code is interpreted or compiled, not
  > how it is compiled.  I don't buy the notion that a byte-compiled
  > function is somehow "less compiled" because it's not compiled to
  > native code.

I didn't see the beginning of the thread, but IMVHO byte-code is both
compiled and interpreted.

kai
-- 
Life is hard and then you die.


  parent reply	other threads:[~1998-10-26  8:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-25  5:24 Lars Magne Ingebrigtsen
1998-10-25  6:01 ` Shenghuo ZHU
1998-10-25 16:46   ` Lars Magne Ingebrigtsen
1998-10-25 14:24 ` Hrvoje Niksic
1998-10-25 16:49   ` Lars Magne Ingebrigtsen
1998-10-25 19:45     ` Hrvoje Niksic
1998-10-25 22:27       ` Lars Magne Ingebrigtsen
1998-10-25 22:51         ` Hrvoje Niksic
1998-10-25 23:02           ` Lars Magne Ingebrigtsen
1998-10-25 23:59             ` Hrvoje Niksic
1998-10-26  0:26               ` Lars Magne Ingebrigtsen
1998-10-26  1:17                 ` Hrvoje Niksic
1998-10-26  8:07               ` Kai Grossjohann [this message]
1998-10-26 13:00 ` Ignored MIME types! Hrvoje Niksic
1998-10-26 15:58   ` Wes Hardaker
1998-10-27 13:14     ` Robert Bihlmeyer
1998-10-26 21: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=vafr9vvu4pf.fsf@ramses.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /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).