[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] FYI, merged in a bunch of changes
|
I have removed the filter because it just hides the
problem. The since tag should read @since 5.2, shouldn't it?
After all you cannot introduce API by adding it to 5.0.3
and then claim it has been part of 5.1.
Markus.
What is the version of the .api_filters file of
org.eclipse.cdt.core that you have.
I'm running version 1.4 which does not seem to have that
filter anymore.
The error is that @since 5.0.3 should be @since
5.2
What error do you see? Chris added API filter but I don't see any
error even after removing the filter and recompiling.
I looked at
ErrorParserManager and the new FileSystemUtility classes and the first
impression that it makes sense although I'd rather advocate the new API in
next release at that point (unless there is a good reason). But it shouldn't
have been added this way after M7 with no bugzilla, no discussion and no
advance notification on cdt-dev.
Andrew
On Wed, May 12, 2010 at 8:58 AM, Marc Khouzam
<marc.khouzam@xxxxxxxxxxxx>
wrote:
IFilesystemUtility is giving
an API tooling error.
I didn't fix it because it was not clear
what you guys will do about this class.
I
agree. We should undo the change and open a bug to discuss the required
change.
Markus.
The descriptions of IFilesystemUtility methods seem too
vague to really specify the behavior. Some terms, e.g. target machine,
mapped filesystem, are used without being clearly defined. I'm against
making this API change so late in the release cycle.
-sergey
On Tue, May 11, 2010 at 3:55 PM, Chris Recoskie
<recoskie@xxxxxxxxxx> wrote:
- Merged changes from cdt_5_0 to HEAD. Too many
to mention individually.
- Reworked
IFileSystem utility so that now it is noimplement/noextend. Clients should
now extend from concrete class FileSystemUtility instead to better
insulate them from future API changes.
-
Reworked the resulting concurrency fixes - indexing and scanner
discovery now synchronize on the project root as a scheduling rule.
Original HEAD behaviour was to synch on the project's .settings folder for
indexing, but that deadlocked with scanner discovery. James, you
will probably want to take a look at what I did there and make sure
you are comfortable with it, as I know you have been trying to relax
the scheduling rules as much as possible. If you think it needs some
rework let me know.
- Fixed remote
indexing. Changes on HEAD that deprecated CodeReader broke the
ability for remote translation units to provide the path to load the
file content from. Added API to ITranslationUnit for this
purpose.
The tests all pass, but let
me know if you run into any problems, particularly if you encounter
any concurrency issues.
FYI error
parsing seems broken for remote projects. I intend to start looking
into that
tomorrow.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM
Toronto
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev