CEDET

Hi Eric,
 
i'm currently kicking away the support for old semantic 1.4, eieio 0.X and speedbar 0.X - i.e. beginning with next release ECB will only work with a ful installed cedet-version...
 
Therefore the question: Which cedet-version should i require as minimum (current = 1.0pre7)? are there previous versions which are quite stable....
 
Another question: Is it possible that a user has installed and loaded cedet and after that shadows this cedet by loading (by accident) an old semantic 1.4 for example?? So, ECB would detect a cedet-version 1.0XXX and a semantic-version 1.4.X.. is this possible? Or has cedet some smart mechanisms to prevent from this?
 
Thanks for info!
 
Klaus
 
____________________________________________________________

Klaus Berndl / Capgemini sd&m / München
Senior-Berater / Öffentlicher Sektor
Tel: +49 89 63812-392 / Fax: +49 89 63812-444 / http://www.de.capgemini-sdm.com <http://www.de.capgemini-sdm.com/> 
Mobil: +49 162 2842051 / klaus.berndl@...
Capgemini sd&m AG, Carl-Wery-Straße 42, 81739 München
____________________________________________________________

Vorstand: Edmund Küpper (Vorsitzender), Burkhard Kehrbusch, Rüdiger Azone,
Dr. Uwe Dumslaff, Kai Grambow, Dr. Michael Rading, Josef Ranner
Aufsichtsrat: Pierre Hessler (Vorsitzender)
Sitz und Amtsgericht: München HRB 126057

Re: [CEDET-devel] good base for ECB - version? From: Eric M. Ludlam <eric@si...> - 2009-04-21 12:38 >>> <klaus.berndl@...> seems to think that: >Hi Eric, >=20 >i'm currently kicking away the support for old semantic 1.4, eieio 0.X = >and speedbar 0.X - i.e. beginning with next release ECB will only work = >with a ful installed cedet-version... >=20 >Therefore the question: Which cedet-version should i require as minimum = >(current =3D 1.0pre7)? are there previous versions which are quite = >stable.... I think each release has gotten more stable. The feature gap between each is large too. If I recall, I have fixes I need to release for ECB now, right? >Another question: Is it possible that a user has installed and loaded = >cedet and after that shadows this cedet by loading (by accident) an old = >semantic 1.4 for example?? So, ECB would detect a cedet-version 1.0XXX = >and a semantic-version 1.4.X.. is this possible? Or has cedet some smart = >mechanisms to prevent from this? [ ... ] CEDET detects and will shadow pre-installed older versions. Sometimes those versions are already loaded when CEDET gets a chance and bugs occur. In that case, stuff needs to be reconfigured. Eric -- Eric Ludlam: eric@... Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net

Re: [CEDET-devel] good base for ECB - version? From: <klaus.berndl@ca...> - 2009-04-21 13:00 >I think each release has gotten more stable. The feature gap between each is large too. Well, then i will require 1.0pre6 (cedet-version) which is available as package from your website... >If I recall, I have fixes I need to release for ECB now, right? Hmm, not to my knowledge... What do you mean? Besides the indirect-buffer stuff i have nothing in mind... BTW: what do you think about my most recent answer to the bug-report? My summary: For not-clone indirect-buffers neither semantic nor ECB has to bother with indirect-buffers because they will not be setup for semantic... Only with real clones we have to ensure things work correcty... This means for GNU Emacs: created by clone-indirect-buffer or with make-indirect-buffer and third argument clone is not nil (e.g. if called from within elisp)...for Xemacs this means: No clones at all - Xemacs can not create indirect-buffer-clones... Probably your clone-indirect-buffer-hook solution would be good in 99% of all cases but nor for all - therefore i still vote for an after-advice for make-indirect-buffer which contains as code: (if (and (not (featurep 'xemacs)) (ad-get-arg 2)) ;; third argument clone is not nil ;; clear the toplevel cache )) This would make semantic save for indirect-buffer concerning independend tag-lists... For the after-change-function propagation i have no real preference... >CEDET detects and will shadow pre-installed older versions. Sometimes those versions are already loaded when CEDET gets >a chance and bugs occur. In that case, stuff needs to be reconfigured. Ok, thanks. Ciao, Klaus

Re: [CEDET-devel] good base for ECB - version? From: Eric M. Ludlam <eric@si...> - 2009-04-21 17:47 >>> <klaus.berndl@...> seems to think that: >>I think each release has gotten more stable. The feature gap between each is large too. > >Well, then i will require 1.0pre6 (cedet-version) which is available as package from your website... I will still try to post another version soon. The pre6 release has build and testing issues on several platforms that are now resolved. I haven't made it all the way through my todo lists. I should probably skip some of those to help out here. >>If I recall, I have fixes I need to release for ECB now, right? > >Hmm, not to my knowledge... What do you mean? Besides the indirect-buffer stuff i have nothing in mind... > >BTW: what do you think about my most recent answer to the bug-report? >My summary: For not-clone indirect-buffers neither semantic nor ECB has to bother with indirect-buffers because they will not be setup for semantic... >Only with real clones we have to ensure things work correcty... This means for GNU Emacs: created by clone-indirect-buffer or with make-indirect-buffer and third argument clone is not nil (e.g. if called from within elisp)...for Xemacs this means: No clones at all - Xemacs can not create indirect-buffer-clones... >Probably your clone-indirect-buffer-hook solution would be good in 99% of all cases but nor for all - therefore i still vote for an after-advice for make-indirect-buffer which contains as code: > > (if (and (not (featurep 'xemacs)) (ad-get-arg 2)) ;; third argument clone is not nil > ;; clear the toplevel cache > )) > >This would make semantic save for indirect-buffer concerning independend tag-lists... > >For the after-change-function propagation i have no real preference... I agree. I think the hook is a fine solution. I like your advice too, though it could turn around, and just call the hook as it now does in Emacs 23 (in CVS). Eric -- Eric Ludlam: eric@... Siege: http://www.siege-engine.com Emacs: http://cedet.sourceforge.net

1 message has been excluded from this view by a project administrator.