|
From: | GNU bug Tracking System |
Subject: | [debbugs-tracker] bug#21013: closed (Evaluation expression from C assumes that lambda is present) |
Date: | Fri, 24 Jun 2016 07:55:02 +0000 |
Your message dated Fri, 24 Jun 2016 09:53:51 +0200 with message-id <address@hidden> and subject line Re: bug#21013: Evaluation expression from C assumes that lambda is present has caused the debbugs.gnu.org bug report #21013, regarding Evaluation expression from C assumes that lambda is present to be marked as done. (If you believe you have received this mail in error, please contact address@hidden) -- 21013: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21013 GNU Bug Tracking System Contact address@hidden with problems
--- Begin Message ---Subject: Evaluation expression from C assumes that lambda is present Date: Wed, 8 Jul 2015 20:48:38 +0200 When using the profiler in a pure module ,profile does not workThe reason is that inscmsigs.c,At an evaluation occurs from C e.g.static SCMclose_1 (SCM proc, SCM arg){return scm_primitive_eval_x (scm_list_3 (scm_sym_lambda, SCM_EOL,scm_list_2 (proc, arg)));}This means that languages in guile that want's profiling needs to export lambda from (guile). Maybe this is a feature but there are two things that can improve,1. We can export @@ or @ as the only symbol from guile and fix all evaluatoins like the above to issue a (@ (guile) lambda) in stead of lambda etc. Maybe we should use a more uncommon symbol for @ and @@ to be used in situations like that for which should always be reexported for langagesthat want to support guile features.lambda is a very common symbol and I would expect profiling to fail under elisp no so this issues seams to be urgent. I will for know export lambda.RegardsStefan
--- End Message ---
--- Begin Message ---Subject: Re: bug#21013: Evaluation expression from C assumes that lambda is present Date: Fri, 24 Jun 2016 09:53:51 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) On Wed 08 Jul 2015 20:48, Stefan Israelsson Tampe <address@hidden> writes: > When using the profiler in a pure module ,profile does not work > > The reason is that in > scmsigs.c, > > At an evaluation occurs from C e.g. > > static SCM > close_1 (SCM proc, SCM arg) > { > return scm_primitive_eval_x (scm_list_3 (scm_sym_lambda, SCM_EOL, > scm_list_2 (proc, arg))); > } Amusing! I tried to work around this use of `eval' but I can't because there's too much C sclerosis. Instead I switched to use scm_eval and specified a module; should fix the issue. Andy
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |