all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Pierre Lorenzon <devel@pollock-nageoire.net>
Cc: zappo@gnu.org, 20507@debbugs.gnu.org
Subject: bug#20507: 25.0.50 eieio and packages depending on it
Date: Tue, 05 May 2015 14:56:56 -0400	[thread overview]
Message-ID: <jwvfv7ax3ij.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <20150505.100641.159216149369481177.devel@pollock-nageoire.net> (Pierre Lorenzon's message of "Tue, 05 May 2015 10:06:41 +0200 (CEST)")

> I already posted two bug reports 20467 and 20491 but each time
> I correct something I get a new error.

I'm sorry about that.  When I installed those changes in EIEIO there were
a few bugs reported, but since then, it's been fairly quiet, so I was
under the impression that things are mostly OK.

> Anyway I suspect that eieio implementation has been change
> without doing necessary modification in codes that use
> eieio.

I did test the new code against CEDET's use, but in only fairly limited
ways (mostly, enabling semantic-mode and using it to perform completion
on a struct field name in regex.c).

> Anyway I wonder why my bug report 20647 where I proposed patches to
> correct some errors got no answer.  Time problem probably.

Yup.  Have you had a chance to try my reply in bug#20491?

> But if you need help for the eieio stuff please simply tell me.

Please do send more of those bug reports and (especially) patches.
Recipes to reproduce those problems are also very welcome (test cases
to add to test/automated are even better), since in many cases I have no
idea how the code is supposed to be used.

> I think I am able to contribute to that. But please tell me
> more precisely which are the goals so that I do not make
> something that is not in the spec ! Or simply tell me if
> there's a good place to know what has to be done with the eieio
> project and all its dependencies.

Mostly what needs to be done is to make sure that old code still works,
and when it doesn't decide whether it should be fixed by changing EIEIO
to be more bug-compatible or by changing the old code.


        Stefan





  reply	other threads:[~2015-05-05 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05  8:06 bug#20507: 25.0.50 eieio and packages depending on it Pierre Lorenzon
2015-05-05 18:56 ` Stefan Monnier [this message]
2015-05-06  0:58   ` Eric Ludlam
2015-05-06 14:52     ` Stefan Monnier
2015-05-06  3:57   ` Pierre Lorenzon
2016-07-29  0:51 ` npostavs

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

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

  git send-email \
    --in-reply-to=jwvfv7ax3ij.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=20507@debbugs.gnu.org \
    --cc=devel@pollock-nageoire.net \
    --cc=zappo@gnu.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.