CEDET

Hello,

I write tests for python. To make python tests pass without errors in
`semantic-ia-utest'  you need to set `comment-start-skip' a value "#":

(add-hook 'python-mode-hook
          (lambda ()
            (setq comment-start-skip "#")))

Now in python-mode `semantic-ia-utes' is nil.
My first test succeeded:
---------------------------------------------------
def moo():
    pass

def main():
    m# -1-
# #1# ( "main" "moo")
---------------------------------------------------

Then I try to make test for classes:
---------------------------------------------------
class Class1:

    def foo1(self):
        pass

class Class2(Class1):

    def foo2(self):
        pass

def main():

    c1 = Class1()
    c1.f# -1-
# #1# ("foo1")

    c2 = Class2()
    c2.f# -2-
# #2# ("foo1" "foo2")
---------------------------------------------------

Test fails with the following errors:

  ** Starting tests in testclass.py
    Failed 1.  Desired: ("foo1") Actual nil
    Failed 2.  Desired: ("foo1" "foo2") Actual nil
    Unit tests (completions) failed tests (1 2)
  ** Completed tests in testclass.py

Why can't semantic find functions for the contexts 1 and 2?

-- 
Regards, Andrey



-- 
Regards, Andrey

Hi,

test.h:

class Bar {
public:
    void dum() { }
};

class Foo {
    Bar baz;

    void test();
};


test.cpp:

#include "test.h"


void wrong()
{
    Bar baz;

    baz.dum();
}

void Foo::test()
{
    baz.dum();
}


Now go over "Bar baz;" line within Foo definition and hit C-c , G.
The result is that CEDET finds two references in the wrong()
function in addition to the only correct one in Foo::test().

-- 
Hannu

Hi,

Current Bazaar version of CEDET doesn't seem to be able to parse
classes in Qt headers of version 4.6.2 (the one in Ubuntu 10.04LTS)
even though I set it up according to some found suggestions that I
believe used to work a long time ago when I tested this:

  (loop for dir in (directory-files qt4-include-base-dir t "^Q")
        do (semantic-add-system-include dir 'c++-mode))
  (semantic-add-system-include qt4-include-base-dir 'c++-mode)
  (add-to-list 'auto-mode-alist (cons (expand-file-name qt4-include-base-dir) 'c++-mode))
  (add-to-list 'semantic-lex-c-preprocessor-symbol-file (concat qt4-include-base-dir "/Qt/qconfig.h"))
  (add-to-list 'semantic-lex-c-preprocessor-symbol-file (concat qt4-include-base-dir "/Qt/qconfig-dist.h"))
  (add-to-list 'semantic-lex-c-preprocessor-symbol-file (concat qt4-include-base-dir "/Qt/qglobal.h"))

If I remove Q_CORE_EXPORT from class declarations, they are recognized.

Btw, about the need to fiddle with lex-c-preprocessor stuff,
EmacsWiki says: "The reason for this is that Semantic does not
parse every #define'd symbol out there - this would simply make
parsing too slow."  Is that really correct?  If it is, can I enable
parsing of all symbols so that manual configuration wouldn't be
needed?

-- 
Hannu

Hi,
when I try to checkout

$ bzr branch 'bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/'

I get this error:
bzr: ERROR: Not a branch: "bzr://cedet.bzr.sourceforge.net/bzrroot/cedet/"


I use
$ bzr --version

Bazaar (bzr) 2.0.3
  Python interpreter: /usr/bin/python 2.5.2
  Python standard library: /usr/lib/python2.5
  Platform: Linux-2.6.26-2-amd64-x86_64-with-debian-5.0.6
  bzrlib: /usr/lib/python2.5/site-packages/bzrlib
  Bazaar configuration: /home/.bazaar
  Bazaar log file: /home/.bzr.log

Copyright 2005, 2006, 2007, 2008, 2009 Canonical Ltd.
http://bazaar-vcs.org/

bzr comes with ABSOLUTELY NO WARRANTY.  bzr is free software, and
you may use, modify and redistribute it under the terms of the GNU
General Public License version 2 or later.

Thanks for your help,
Alexander

-- 
"I can't understand why people are frightened of new ideas.
 I'm frightened of the old ones.”
 - John Cage

Hannu Koivisto <azure@...> writes:

> I guess I'll have to look at one of those git-bzr bridges such as
> https://github.com/termie/git-bzr-ng and try setting up a mirror
> myself.

Well, git-bzr-ng seems to work, I created a test mirror at
<git://gitorious.org/cedet-mirror/cedet-mirror.git>.  I'm not
updating it automatically at least until new commits appear and I
can test updating.

-- 
Hannu