[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Compiled code in Emacs-26 will fail in Emacs-25 if use pcase [was: A

From: raman
Subject: Re: Compiled code in Emacs-26 will fail in Emacs-25 if use pcase [was: Add new bytecode op `switch' for implementing branch tables.]
Date: Thu, 23 Feb 2017 08:15:40 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

Tino Calancha <address@hidden> writes:

Likely related, I'm also noticing
 that code that compiles and run correctly against 25.1 and that used to
 compile and run error-free on Master just started breaking,
I'm still working on creating a small repro case.

But what I'm noticing:

With code compiled with lexical scoping,  defsubst forms appear to
behave differently when compiled vs evaled --- eval: no error, compile
and load == error.
> Sorry if this is obvious, then just ignore.
> I have a custom lib using `pcase' somewhere.  That lib is
> compatible with Emacs25.
> Usually i compile this lib against the master branch.  Then, i load
> that very same resulting .elc in Emacs-25 and runs same as in Emacs-26.
> (Maybe this is just wrong and i must keep separated .elc)
> After the new bytecode those parts of the lib using pcase fail.
> For instance, put the following in a file:
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> (defun test-case ()
>   (let ((val "foo"))
>     (pcase val
>       ("foo" "foo")
>       ("bar" "bar")
>       (_ (error "Neither 'foo' nor 'bar'")))))
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
> I) Compile under master branch.
> II) Load the resultant .elc with Emacs-25
> II) M-: (test-case)
> ;; Signal error: Invalid byte opcode: op=183, ptr=4
> So, in conclusion:
> From now on, we need to keep two separated .elc in such custom libs,
> right?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]