CEDET

>>> Vadim Zyarko <vzyarko@...> seems to think that:
>Cedet shows some examples of unprofessional &
>neglectful behavior, may be suitable for young, hairy
>brained hackers, but not acceptable in the
>professional society. 
>It just killed my Makefile silently, when I tried it
>for the first time. In the 'preference' game you can
>get a candelabra in the face for such tricks.
  [ ... ]

Since the best I can do is guess wildly what you might have been
typing into your computer, I have checked in some random code that
shares a few nouns with your message.

---
revision 1.44
date: 2004/12/15 04:26:12;  author: zappo;  state: Exp;  lines: +6 -1
(ede-proj-makefile-create): Ask before whacking a Makefile.
---

Eric

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

Hi,

  I have discovered that doing this after starting an ECB/speedbar layout:

(setq dframe-after-select-attached-frame-hook nil)

  solves the problem.  It also solves a problem where you cannot do
any repetitive speedbar keyboard commands.

  The value that was there was an ECB function which would re-select
the original working window.

Eric

>Hello all. This is a revival of old thread I started in October 2005. I
>have upgraded my ecb version to 2.33beta1 and was hoping that this issue
>would magically go away. Unfortunately, it is still present.
>
>I can defintely remove the (setq speedbar-update-flag t) from my init
>function, but I think it would be good to understand why the behavior
>changed from one version of cedet to the next.
>
>I tried M-: (setq speedbar-dynamic-tags-function-list (cdr
>speedbar-dynamic-tags-function-list)) and the problem still happened.
>
>Any other thoughts or does everyone want to me to shut up about this?
>;-)
>
>Thanks.
>
>Javier

-- 
          Eric Ludlam:                 zappo@..., eric@...
   Home: http://www.ludlam.net            Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net               GNU: http://www.gnu.org

hi, 
I am working on a php project using cedet. There seems to a parsing problem with the "define()" function. 
The file looks like below.
define('SOME_CONST', 0);
class some_class{

}

I run "bovinate". It comes back with no tags.
I run "semantic-describe-buffer". Here is the result.
Semantic Configuration in some_file.php
Buffer specific configuration items:  major-mode: #'php-mode  semantic-case-fold: : nil  semantic-tag-expand-function: #'semantic-expand-c-tag  semantic-parser-name: "LALR"  semantic-parse-tree-state: : nil  semantic-lex-analyzer: #'wisent-php-lexer  semantic-lex-reset-hooks:  #<list of 2 items>    #'semantic-lex-spp-reset-hook    't  semantic-lex-syntax-modifications:  #<list of 2 items>    #<list o' stuff: 2 entries>    #<list o' stuff: 2 entries>
General configuration items:  semantic-inhibit-functions: : nil  semantic-init-hook: #<list o' stuff: 12 entries>  semantic-init-db-hook:  #<list of 1 items>    #'semanticdb-semantic-init-hook-fcn  semantic-unmatched-syntax-hook: : nil  semantic--before-fetch-tags-hook: : nil  semantic-after-toplevel-bovinate-hook: : nil  semantic-after-toplevel-cache-change-hook:  #<list of 4 items>    #'semantic-imenu-flush-fcn    #'senator-completion-cache-flush-fcn    #'semantic-decorate-tags-after-full-reparse    't  semantic-before-toplevel-cache-flush-hook:  #<list of 2 items>    #'semantic-mrub-cache-flush-fcn    #'semantic-edits-flush-changes  semantic-dump-parse: : nil  semantic-type-relation-separator-character:  #<list of 3 items>    "."    "->"    "::"  semantic-command-separation-character: ";

If I commet out the define function before the class definition, and then run "bovinate". The class will be successfully parsed.
Any solution to this?

Yang Liu writes:
> hi, 
> I am working on a php project using cedet. There seems to a parsing problem with the "define()" function. 
> The file looks like below.
> define('SOME_CONST', 0);
> class some_class{
>
> }
>
> I run "bovinate". It comes back with no tags.

CEDET doesn't parse PHP by default. There is a Wisent parser for PHP in
the contrib directory, but without the necessary overrides, I'm afraid
the PHP support is not really usable. (I have actually no idea, since I
don't code PHP, but that's what I remember from previous discussions in
this list).

-David