[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-devel
Subject: Re: Code completion, code hinting, code browsing
From: Daniel Engelschalt <s2697 () htw-dresden ! de>
Date: 2001-10-29 6:40:12
[Download RAW message or body]
On Fri, 26 Oct 2001, Thomas Schilling wrote:
> Hello Daniel,
>
> You wanted a _complete_ list of possible function declarations but you want
> to make a _simple_ parser (or code inspector)? Well, I found out that this is
> probably not compatible.
> As I tried to just extract the rules needed for declarations it became more
> and more rules. And than it made senso to me: In C++ you can put a whole
> class delaration as the type for your variable, which brings you to function
> declarations, this to function definitions (so functions with
> bodies) and then there's nothing much left of the full C++ grammar.
ok, IMO these things should be placed in the header files where they
can be parsed by the classparser we already have and skipped by our
parser (or we create a new parser that can handle .h and .cpp files
correctly - but i think it's a _lot_ of work :)
> So what should we do? I can send it to you but it'll be some tipping work
> <:-|.
no, you don't need to - was just an idea from me :)
> Where can I find gideon?
via cvs or at ftp.kdevelop.org
take a look at what we have done and if we can continue that way or
not. you can mail me privately to discuss all these things at
daniel.engelschalt@htw-dresden.de
daniel
--
Prepare to destroy the Borg! Ensign, upload Windows!
-
to unsubscribe from this list send an email to kdevelop-devel-request@kdevelop.org \
with the following body: unsubscribe »your-email-address«
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic