unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 31742@debbugs.gnu.org
Subject: bug#31742: 26.1.50; excorporate.elc byte-compiled in Emacs 25.x fails in Emacs 26.1
Date: Wed, 06 Jun 2018 21:14:47 -0400	[thread overview]
Message-ID: <87po132y9k.fsf@gmail.com> (raw)
In-Reply-To: <m336xz76ba.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Wed, 06 Jun 2018 21:07:21 -0400")

Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:

> soap-find-operation: Wrong type argument: soap-binding, ("http://schemas.microsoft.com/exchange/services/2006/messages" . "ExchangeServiceBinding")

> byte code for exco--bind-wsdl:
>   doc:  Create a WSDL binding. ...
>   args: (arg1 arg2 arg3 arg4 arg5)
> 0	constant  soap-wsdl-find-namespace
> 1	stack-ref 2
> 2	stack-ref 6
> 4	call	  2
> 5	constant  vector
> 6	constant  cl-struct-soap-port

> byte code for exco--bind-wsdl:
>   doc:  Create a WSDL binding. ...
>   args: (arg1 arg2 arg3 arg4 arg5)
> 0	constant  soap-wsdl-find-namespace
> 1	stack-ref 2
> 2	stack-ref 6
> 4	call	  2
> 5	constant  record
> 6	constant  soap-port

Looks like it's due to the change in how cl-struct works.  Does enabling
cl-old-struct-compat-mode help?

    cl-old-struct-compat-mode is an interactive autoloaded compiled Lisp
    function in ‘cl-lib.el’.

    (cl-old-struct-compat-mode &optional ARG)

    Enable backward compatibility with old-style structs.
    This can be needed when using code byte-compiled using the old
    macro-expansion of ‘cl-defstruct’ that used vectors objects instead
    of record objects.






  reply	other threads:[~2018-06-07  1:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  1:07 bug#31742: 26.1.50; excorporate.elc byte-compiled in Emacs 25.x fails in Emacs 26.1 Thomas Fitzsimmons
2018-06-07  1:14 ` Noam Postavsky [this message]
2018-06-07  2:01   ` Thomas Fitzsimmons
2018-06-07 12:21     ` Noam Postavsky
2018-06-07 14:06       ` Thomas Fitzsimmons
2018-06-07 17:36         ` Noam Postavsky
2018-06-08  1:13           ` Thomas Fitzsimmons
2018-06-08  1:57             ` Noam Postavsky
2018-06-08  2:17               ` Thomas Fitzsimmons
2018-06-08 12:19                 ` Noam Postavsky
2018-06-08 14:18                   ` Thomas Fitzsimmons
2018-06-09  0:01                     ` Alex Harsanyi
2018-06-09  2:54                       ` Thomas Fitzsimmons
2018-06-09  9:13                         ` Alex Harsanyi
2018-06-09 10:32                           ` Thomas Fitzsimmons
2018-06-12  1:55                           ` Thomas Fitzsimmons
2018-06-12 17:11                             ` Eli Zaretskii
2018-06-13  1:39                               ` Thomas Fitzsimmons
2018-06-17  0:12                             ` Alex Harsanyi
2018-06-17  0:36                               ` Thomas Fitzsimmons
2018-06-17  1:31                                 ` Alex Harsanyi
2018-06-17  1:36                                   ` Noam Postavsky
2018-06-17 13:02                                   ` Thomas Fitzsimmons
2018-06-09 10:30                       ` Thomas Fitzsimmons
2018-06-09 12:13                         ` Noam Postavsky

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87po132y9k.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31742@debbugs.gnu.org \
    --cc=fitzsim@fitzsim.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).