From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/18169 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Pterodactyl Gnus v0.39 is released Date: 26 Oct 1998 00:02:33 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035156740 4764 80.91.224.250 (20 Oct 2002 23:32:20 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:32:20 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA03680 for ; Sun, 25 Oct 1998 18:49:33 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAB26664; Sun, 25 Oct 1998 17:49:21 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 25 Oct 1998 17:49:02 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id RAA12937 for ; Sun, 25 Oct 1998 17:48:53 -0600 (CST) Original-Received: from sparky.gnus.org (ppp041.uio.no [129.240.240.42]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id SAA03661 for ; Sun, 25 Oct 1998 18:48:48 -0500 (EST) Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id AAA32534; Mon, 26 Oct 1998 00:48:43 +0100 Mail-Copies-To: never X-Now-Reading: Amy Hempel's _Reasons to Live_ X-Now-Playing: Stereolab's _Aluminium Tunes [Switched On 3] (cd2)_: "Seeperbold" Original-To: ding@gnus.org In-Reply-To: Hrvoje Niksic's message of "25 Oct 1998 23:51:24 +0100" User-Agent: Gnus/5.070041 (Pterodactyl Gnus v0.41) Emacs/20.3 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > I disagree with your distinction of "really compiled" vs. > "byte-compiled" functions. It makes as much sense for compiled > functions to be called just that. The type of the compilation is an > implementation detail. I don't think so. The difference between Lisp and byte-code is in many ways as big as the difference between byte-code and native code. For instance, you can instrument byte-compiled functions, but you can't instrument natively compiled code. You can inspect many things inside byte-compiled code; you can't do that with native code. You can get understandable backtraces with errors in byte-compiled code; do don't with native code. Byte-compiled code can't segfault on you; native code can. Etc. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen