From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.help Subject: Re: Strange eval behaviour Date: Fri, 18 Nov 2016 03:38:25 +0100 Message-ID: <878tshjyvy.fsf@web.de> References: <87vavrul0k.fsf@mail.de> <878tsl1p7b.fsf@mail.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1479436755 13223 195.159.176.226 (18 Nov 2016 02:39:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 18 Nov 2016 02:39:15 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) Cc: help-gnu-emacs@gnu.org To: Stefan Huchler Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Nov 18 03:39:07 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c7Z50-0001Pb-9i for geh-help-gnu-emacs@m.gmane.org; Fri, 18 Nov 2016 03:39:06 +0100 Original-Received: from localhost ([::1]:34303 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7Z52-0000eP-5P for geh-help-gnu-emacs@m.gmane.org; Thu, 17 Nov 2016 21:39:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c7Z4X-0000e8-Dc for help-gnu-emacs@gnu.org; Thu, 17 Nov 2016 21:38:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c7Z4U-0005Uw-7n for help-gnu-emacs@gnu.org; Thu, 17 Nov 2016 21:38:37 -0500 Original-Received: from mout.web.de ([212.227.17.12]:60843) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c7Z4T-0005Uh-Tt for help-gnu-emacs@gnu.org; Thu, 17 Nov 2016 21:38:34 -0500 Original-Received: from drachen.dragon ([90.186.1.95]) by smtp.web.de (mrweb102 [213.165.67.124]) with ESMTPSA (Nemesis) id 0LjJL9-1cdJzF0Bcl-00dVCp; Fri, 18 Nov 2016 03:38:30 +0100 In-Reply-To: <878tsl1p7b.fsf@mail.de> (Stefan Huchler's message of "Tue, 15 Nov 2016 02:55:52 +0100") X-Provags-ID: V03:K0:HGDiwTCYoSiSCbS19MMVdO6lXfoIlDhTO6C9ce57yuO/nQyw/gn KPBmWuz9Bx+aDAaXK39bklc38T54wZWkXK9jC9V40qclehAmezPHtX+1vpz9m3rbeOoQTlI Iwq4BIHAojP+R5A2Z6/nbCQF5ySlpFMSuTI6yzXYrs7JsSkfLpW7UY+rA5UHcy+iTuU0DL4 16kEmLP6MuR0sDbHuNe5A== X-UI-Out-Filterresults: notjunk:1;V01:K0:pjbh8IZpusU=:GUO9USxhW+TaSlbbrDe3d4 P2mu3af+LYxhL8r4a8jDhoZpz1GPBbSYIF/lvtHHb0rIcddPA9sl2ENP2uDpqOvp/k4HAEQN5 9+VsBcDBaqBqm7q3itpPQKtqkEGsBj05LpKYHIJXTKDdCqT9jfhJv8ed03GCAh7Z+g819Py7O Xg6UNaWs5Sn4rdL8gTq1a+mivwgdqd8IKvyjhtPI9dX0cOwGtKPmwkaUnjf5FuxV8AUZHAbM+ UZykbsOTY7PiNpf3w4FxDFb0R4UUVaje3p3zPOytrTl8KOUPjrPYFa8Yba0/lch82DBeu4cCw jkiPjpK/FnwRdPo3/SjpTcDkJnofjE1ZSiTKoOacMRb2OhlQDqQVLaLyEzrCJhZ7tFvoOpLgm xO8UNnvwUPFclTxH2ePSIYZ3kXfsN0eu3mTUblVJolTTJOx+Rybmce6+Zpp0WhvJ+zz1mZ8dU dURBmPQEeNXY5qNOrL16lvuVyY9OK+voowMk9GSRj9hL7FUUEvq4nSdxi9RhPFsFv3Ng124kh IuBnqQix/p+1bZsdGCkPUBaIEoh6jzBw/OPRYtf5apGeEq7IRQz4bikuvcGv0IT3okq/2Kb4C g72nErR576D2Xr5oLuvnkA+b0MrSmO6Bzu3iD44/XM98dbIFxELX1vc2Lwl9KcgngZMutMh3Z BOI8qtGPnZMqR1P9fU8lwbDzp+RzXYizztu2Z7uglNh3mysN+l9qGGGdvM/Df1DHznTm0xhX8 o0baYz3hz3NJ6afCE8goSxFKgqjyrv74XWDfqmf2+9n5FLTx7Fb1hv9bZcKGJGdzEUyYXtCh X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 212.227.17.12 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:111738 Archived-At: Stefan Huchler writes: > Normaly it should through a error if it cant find a macro/function > that is not availible right? In case of a macro, it depends on whether the macro is defined when compiling. So you don't get a warning necessarily. To avoid missing dependencies, it's helpful to compile from a separate emacs instance (emacs -Q). > that was the code I did not have > (require 'let-alist) That was one problem, at least. > in the file? > Again thanks so far so I can release that code soon, but again I would > like to understand what the problem was. AFAIR, you had a strange handling of variables in your code: some functions had used free variables that were declared nowhere. Compiling is a good way to reveal such problems. > Do I have to have a byte-compiled .elc file if I use the "function" > macro No. > oh wait its the function* which is a alias to the cl-function macro in > cl-macs > > so I need the cl library imported too. Yes. It is now more or less consent now that the cl library should not be loaded at run-time. Please use cl-lib and the according cl- prefixed functions instead. > But well thats more relevant for packaging I think, I think the main > problem was that there just was no .elc file? No, Stefan suggested to compile so that you get warnings that help you find the problems in your code. Compiling is not required to run code. Compiled code is just running faster, and the compiler produces excellent warnings. Michael.