[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 160143] find in files: search in included files
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2008-03-31 10:26:03
Message-ID: 20080331102603.4742.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=160143         
apaku gmx de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      everconfirmed|0                           |1



------- Additional Comments From apaku gmx de  2008-03-31 12:26 -------
#6: Find-In-Files won't be language specific, it cannot depend on C++ support, it \
won't ever know that these are #include directives. However luckily our language \
support already has ways of expression that at this point there are symbols imported \
into the current context that come from different files. Also IIRC we have support to \
get at the actual filename for such imported context. So this will actually work for \
all languages that support import/include directives, when it is implemented. So all \
that can fail is the language support finding the actual file that is \
imported/included and thus it can't parse it.

Thats KDevelop4 material - of course.

And btw: Thinking about this a bit more, I actually like the idea of utilizing our \
language-infrastructure to support this.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs


[prev in list] [next in list] [prev in thread] [next in thread]