[Top][All Lists]

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

bug#20507: 25.0.50 eieio and packages depending on it

From: Pierre Lorenzon
Subject: bug#20507: 25.0.50 eieio and packages depending on it
Date: Wed, 06 May 2015 05:57:24 +0200 (CEST)

Hi Stefan

Thanks for your answer.

From: Stefan Monnier <address@hidden>
Subject: Re: bug#20507: 25.0.50 eieio and packages depending on it
Date: Tue, 05 May 2015 14:56:56 -0400

>> 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.

  Unfortunately it is maybe not exactly the case and there is
  still things to improve. Anyway I cannot say how much there's
  to do. In fact I discover the bugs each one after another.

>> 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).

  OK That's why bugs in ede implementation for instance have
  not been detected. Anyway I'll continu to track them !

>> 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?

  Yes I did the modification to the code that you suggested and
  it fixed the bug at this place.

>> 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.

  No problem I'll try to make the stuff work and send patches.

>> 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

          Thanks again


reply via email to

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