Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] unsubscribe

-----Urspr√ľngliche Nachricht-----
Von: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx]Im
Auftrag von cdt-dev-request@xxxxxxxxxxx
Gesendet: Donnerstag, 13. Januar 2005 22:35
An: cdt-dev@xxxxxxxxxxx
Betreff: cdt-dev digest, Vol 1 #905 - 8 msgs


Send cdt-dev mailing list submissions to
	cdt-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
	http://dev.eclipse.org/mailman/listinfo/cdt-dev
or, via email, send a message with subject or body 'help' to
	cdt-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
	cdt-dev-admin@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cdt-dev digest..."


Today's Topics:

   1. EclipseCon BOF update (Sebastien Marineau)
   2. RE: Problem to develop a toolchain (Treggiari, Leo)
   3. RE: CDT2.1: MBS: How to stop the 'build' after compiler phase
(Treggiari, Leo)
   4. RE: MBS in CDT 2.1: Is it possible to build only one file or a set of
files ? (Treggiari, Leo)
   5. RE: Build console not erased (Treggiari, Leo)
   6. CDT-2.1 life cycle (Alain Magloire)
   7. Re: CDT-2.1 life cycle (Douglas Schaefer)
   8. Indexer Requirements for 3.0 (Bogdan Gheorghe)

--__--__--

Message: 1
From: Sebastien Marineau <sebastien@xxxxxxx>
To: cdt-dev@xxxxxxxxxxx
Date: Thu, 13 Jan 2005 11:58:50 -0500
Subject: [cdt-dev] EclipseCon BOF update
Reply-To: cdt-dev@xxxxxxxxxxx

Hi folks,

Sorry for missing the call yesterday, but just wanted to give folks an
update on the EclipseCon sessions. As you probably know, two of the sessions
we submitted were accepted (general CDT session and Redhat's CDT/Eclipse for
Linux session). As for the BOFs, there is no answer yet on the two BOFs we
submitted. The program committe chair told me they were hoping to send out
the confirmations shortly, but that this was not yet finalized.

Just as a reminder, this is what we submitted for BOFs:

Eclipse CDT BOF:

Meet the experts and discuss the implementation and direction of CDT. The
format will likely be a series of mini-overviews on different aspects of CDT
along with open discussions.
Intel, IBM, QNX and Redhat have volunteered to present here. We will also
try to get a few customers to present their experiences.


Remote development and debugging BOF:

TI, HP, Montavista and IBM have expressed strong interest in hosting this.
The main focus would be on the specific challenges of using Eclipse and CDT
in a host/target configuration, both for development and debugging. This
spans the range from deeply embedded (TI) to traditional embedded (Mvista)
to the server/mini types of apps (HP and IBM). I also expect we can get a
couple of customers to participate in this as well.


Thanks,

Sebastien


--__--__--

Message: 2
Subject: RE: [cdt-dev] Problem to develop a toolchain
Date: Thu, 13 Jan 2005 13:42:29 -0500
From: "Treggiari, Leo" <leo.treggiari@xxxxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Reply-To: cdt-dev@xxxxxxxxxxx

The "null null" usually occurs when the Managed Build system cannot find
a tool that produces the file extension specified for the target.  If
that is "r37" in your case, then try adding:

defaultExtension=3D"r37"

to the target definition.

Regards,
Leo


-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Ebert, Ralf
Sent: Thursday, January 13, 2005 2:10 AM
To: cdt-dev (E-Mail)
Subject: [cdt-dev] Problem to develop a toolchain

Hi,

I trying to develop toolchains for Visusal C and a compiler from IAR.
After
I've read the cookbook 'Managed Build System Extensibility Document', I
defined a tiny toolchain, which contain the calls for the compiler and
linker
only. To test the toolchain, I created a project with 'Managed  Make C
Project' and added durectory with a C-File to the project. This file was
compiled right, but the call of the linker failed, because the entry
within
the generated makefile was

 test: $(OBJS)
 @echo 'Building target: $@'
 null null $@ $(OBJS) $(USER_OBJS) $(LIBS)
 @echo 'Finished building: $@'

instead of

 test: $(OBJS)
 @echo 'Building target: $@'
 xlink -o  $@ $(OBJS) $(USER_OBJS) $(LIBS)
 @echo 'Finished building: $@'

Has someone any idea how I can solve the problem or how I can debug a
generated plugin?

The content of the file 'plugin.xml' is:

 <?xml version=3D"1.0" encoding=3D"UTF-8"?>
 <?eclipse version=3D"3.0"?>
 <plugin
 id=3D"org.eclipse.cdt.IAR.toolchain"
 name=3D"Toolchain Plug-in"
 version=3D"1.0.0"
 provider-name=3D"">

 <runtime>
 <library name=3D"toolchain.jar">
 <export name=3D"*"/>
 </library>
 </runtime>
 <requires>
 <import plugin=3D"org.eclipse.cdt.managedbuilder.core"/>
 </requires>
 <extension
 id=3D"org.eclipse.cdt.IAR.toolchain"
 name=3D"IAR Tool Chain"
 point=3D"org.eclipse.cdt.managedbuilder.core.ManagedBuildInfo">
 <target
 isAbstract=3D"false"
=20
errorParsers=3D"org.eclipse.cdt.core.MakeErrorParser;org.eclipse.cdt.core=
.
GCCE
rrorParser;org.eclipse.cdt.core.GASErrorParser;org.eclipse.cdt.core.VCEr
rorPa
rser" osList=3D"win32"
 makeCommand=3D"make"
 isTest=3D"false"
 binaryParser=3D"org.eclipse.cdt.core.PE"
 name=3D"IAR Executable"
 id=3D"IAR.toolchain.executable"
 cleanCommand=3D"rm -f">
 <configuration
 name=3D"Test Release"
 id=3D"IAR.toolchain.release"/>
 <tool
 command=3D"C:\Programme\IAR_Systems\ew23\h8\bin\icch8"
 sources=3D"c,C"
 outputs=3D"r37"
 headerExtensions=3D"h,H"
 name=3D"Compiler"
 outputFlag=3D"-o"
 id=3D"IAR.toolchain.compiler"
 natureFilter=3D"both"/>
 <tool
 command=3D"C:\Programme\IAR_Systems\ew23\h8\bin\xlink"
 sources=3D"r37"
 outputs=3D"mot"
 name=3D"Linker"
 outputFlag=3D"-o"
 id=3D"IAR.toolchain.linker"
 natureFilter=3D"both"/>
 </target>
 </extension>

 </plugin>

best regards,
  Ralf Ebert

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

--__--__--

Message: 3
Subject: RE: [cdt-dev] CDT2.1: MBS: How to stop the 'build' after compiler
phase
Date: Thu, 13 Jan 2005 13:48:03 -0500
From: "Treggiari, Leo" <leo.treggiari@xxxxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Reply-To: cdt-dev@xxxxxxxxxxx

There is currently no easy way to do that.  You could define a separate
projectType/target that does not contain the linker tool.

Regards,
Leo

-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Jerome CORRENOZ
Sent: Thursday, January 13, 2005 7:48 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] CDT2.1: MBS: How to stop the 'build' after compiler
phase

Hello,

I'm using Eclipse 3.0.1 and CDT 2.1.

Is it possible with the MBS to stop the Build after assembling or=20
compiling phase, without launching the linker phase ?
With our compiler, some options don't generate objects files (.o), so=20
the linker fails. It will be better for these options to not launch the=20
linker.
For example:
    -S                  Stop before assembling; output in .s file

Is there a way to do it?

Thanks for advance

--=20
________________________________________________________________

Jerome CORRENOZ                      jerome.correnoz@xxxxxx
STMicroelectronics                   www.st.com
TPA/DSP & Micro Division/Tools
Software Engineer        	     A450-02
12, rue Jules Horowitz - B.P. 217    Phone: +33 (0)4 76 58 68 42
F-38019 GRENOBLE Cedex               Fax:   +33 (0)4 76 58 56 68
________________________________________________________________


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

--__--__--

Message: 4
Subject: RE: [cdt-dev] MBS in CDT 2.1: Is it possible to build only one file
or a set of files ?
Date: Thu, 13 Jan 2005 13:51:11 -0500
From: "Treggiari, Leo" <leo.treggiari@xxxxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Reply-To: cdt-dev@xxxxxxxxxxx

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4F9A0.D9EA54F8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This functionality is not implemented in CDT 2.1.  It's on the Managed
Build system requirements list (see bugzilla # 81450), but I don't think
it is likely to be implemented in CDT 3.0.

=20

Regards,

Leo

=20

________________________________

From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Jerome CORRENOZ
Sent: Thursday, January 13, 2005 7:47 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] MBS in CDT 2.1: Is it possible to build only one file
or a set of files ?

=20

Hello,

Thanks to CDT 2.1, individual files can use different tool options.
It is also possible to excluded specific-files from a build
configuration.

But is it possible to build only one file or a set of files ?

Thanks for your help
Jerome




--=20
________________________________________________________________
=20
Jerome CORRENOZ                      jerome.correnoz@xxxxxx
STMicroelectronics                   www.st.com
TPA/DSP & Micro Division/Tools
Software Engineer                   A450-02
12, rue Jules Horowitz - B.P. 217    Phone: +33 (0)4 76 58 68 42
F-38019 GRENOBLE Cedex               Fax:   +33 (0)4 76 58 56 68
________________________________________________________________

------_=_NextPart_001_01C4F9A0.D9EA54F8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40";>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
tt
	{font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This functionality is not =
implemented in
CDT 2.1.&nbsp; It&#8217;s on the Managed Build system requirements list =
(see
bugzilla # 81450), but I don&#8217;t think it is likely to be =
implemented in
CDT 3.0.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Leo<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] <b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Jerome CORRENOZ<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, January =
13, 2005
7:47 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> <st1:PersonName =
w:st=3D"on">cdt-dev@xxxxxxxxxxx</st1:PersonName><br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [cdt-dev] MBS in =
CDT 2.1:
Is it possible to build only one file or a set of files =
?</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:
10.0pt'>Hello,</span></font></tt><br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Thanks to
CDT 2.1, individual files can use different tool =
options.</span></font></tt><br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>It is also
possible to excluded specific-files from a build =
configuration.</span></font></tt><br>
<font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'><br>
<tt><b><font face=3D"Courier New"><span style=3D'font-weight:bold'>But =
is it
possible to build only one file or a set of files =
?</span></font></b></tt></span></font><br>
<br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Thanks for
your help</span></font></tt><br>
<tt><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>Jerome</span></font></tt><br>
<br>
<br>
<o:p></o:p></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>-- <o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
__________________<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Jerome =
CORRENOZ&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a
href=3D"mailto:jerome.correnoz@xxxxxx";>jerome.correnoz@xxxxxx</a><o:p></o=
:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>STMicroelectronics&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp; <a
href=3D"http://www.st.com";>www.st.com</a><o:p></o:p></span></font></pre><=
pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>TPA/DSP =
&amp; Micro Division/Tools<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Software =
Engineer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;A450-02<o:p></o:p></span></font></pre><pre>=
<font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>12, rue =
Jules Horowitz - B.P. 217&nbsp;&nbsp;&nbsp; Phone: +33 (0)4 76 58 68 =
42<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>F-38019 =
<st1:City
w:st=3D"on"><st1:place w:st=3D"on">GRENOBLE</st1:place></st1:City> =
Cedex&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; Fax:&nbsp;&nbsp; +33 (0)4 76 58 56 =
68<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'>______________________________________________=
__________________<o:p></o:p></span></font></pre></div>

</body>

</html>

------_=_NextPart_001_01C4F9A0.D9EA54F8--

--__--__--

Message: 5
Subject: RE: [cdt-dev] Build console not erased
Date: Thu, 13 Jan 2005 13:58:29 -0500
From: "Treggiari, Leo" <leo.treggiari@xxxxxxxxx>
To: <cdt-dev@xxxxxxxxxxx>
Reply-To: cdt-dev@xxxxxxxxxxx

There is already a bug report for the Managed Build system (76006).  You
should look at that to make sure that it covers your case.  If not, if
it has to do with the Managed Build system, you could add additional
comments there or create a new bugzilla.

Regards.
Leo


-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Leon Pollak
Sent: Thursday, January 13, 2005 10:08 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Build console not erased

Hello,
	My installation is Linux FC1, GTK, Eclipse 3.0.1 CDT 2.1.
	I checked the box Window->Preferences->C/C++->Build
Console->"Always=20
clear console before building" option, but the build console is not=20
cleared even once.
	Is it a bug? If yes, where to report it (Eclipse or CDT, which
module)?
--=20
Dr.Leon M.Pollak
Director
PLR Information Systems Ltd.
leonp at plris dot com

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev

--__--__--

Message: 6
To: cdt-dev@xxxxxxxxxxx
Date: Thu, 13 Jan 2005 16:08:41 -0500 (EST)
From: "Alain Magloire" <alain@xxxxxxx>
Subject: [cdt-dev] CDT-2.1 life cycle
Reply-To: cdt-dev@xxxxxxxxxxx

Bonjour,

  Last conf. call, I suggested the possibility to have a 2.1.1,
the reactions were not very enthusiast ...
Probably, Most participants want to concentrate efforts/resources to get
CDT-3.0 ready ...

So before going to the motions of bugzilla entries, PR scrubing, build
candidates etc ...,
lets make it clear there is a desire for this .. with some {+1, 0, -1}
votes.

It folks would prefer we go full steam toward 3.0 that's fine, too.

--
au revoir, alain


--__--__--

Message: 7
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] CDT-2.1 life cycle
From: Douglas Schaefer <dschaefe@xxxxxxxxxx>
Date: Thu, 13 Jan 2005 16:28:04 -0500
Reply-To: cdt-dev@xxxxxxxxxxx

Well, from our perspective, we do not have product requirements for 2.1.
We have 2.0.x in our current release stream and will be using 3.0.x in the
next. From that angle, we're a 0.

However, if the bugs are severe enough to cause negative feelings with the
open source customers of the CDT, then I'd say +1. I guess that depends on
the list you put together :-)

Doug Schaefer
Ottawa Lab, IBM Rational Software Division



"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx
01/13/2005 04:08 PM
Please respond to
cdt-dev


To
cdt-dev@xxxxxxxxxxx
cc

Subject
[cdt-dev] CDT-2.1 life cycle






Bonjour,

  Last conf. call, I suggested the possibility to have a 2.1.1,
the reactions were not very enthusiast ...
Probably, Most participants want to concentrate efforts/resources to get
CDT-3.0 ready ...

So before going to the motions of bugzilla entries, PR scrubing, build
candidates etc ...,
lets make it clear there is a desire for this .. with some {+1, 0, -1}
votes.

It folks would prefer we go full steam toward 3.0 that's fine, too.

--
au revoir, alain

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev



--__--__--

Message: 8
To: cdt-dev@xxxxxxxxxxx, cdt-patch@xxxxxxxxxxx
From: Bogdan Gheorghe <gheorghe@xxxxxxxxxx>
Date: Thu, 13 Jan 2005 16:32:14 -0500
Subject: [cdt-dev] Indexer Requirements for 3.0
Reply-To: cdt-dev@xxxxxxxxxxx

--=_mixed 00764EAB85256F88_=
Content-Type: multipart/alternative; boundary="=_alternative
00764EAE85256F88_="


--=_alternative 00764EAE85256F88_=
Content-Type: text/plain; charset="US-ASCII"

Here is a list of indexer requirements for the 3.0 release. The overall
focus for the indexer for 3.0 is on improving the scalability and overall
usability of the indexer service for all clients. Feedback is always
appreciated - especially if you think there are missing requirements. A
more detailed design doc is to follow.

Thanks,
Bogdan



--=_alternative 00764EAE85256F88_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Here is a list of indexer requirements
for the 3.0 release. The overall focus for the indexer for 3.0 is on
improving
the scalability and overall usability of the indexer service for all
clients.
Feedback is always appreciated - especially if you think there are missing
requirements. A more detailed design doc is to follow.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif">Bogdan</font>
<br>
<br>
<br>
--=_alternative 00764EAE85256F88_=--
--=_mixed 00764EAB85256F88_=
Content-Type: text/html; name="Indexer3_0_Reqs.html"
Content-Disposition: attachment; filename="Indexer3_0_Reqs.html"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title>Indexer 3.0</title>
  <meta http-equiv=3D"Content-Type"
 content=3D"text/html; charset=3Diso-8859-1">
  <link rel=3D"stylesheet"
 href=3D"http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/cdt-home/c=
dt.css?cvsroot=3DTools=5FProject"
 type=3D"text/css">
</head>
<body>
<!-- Document Header -->
<table style=3D"width: 100%;" border=3D"0" cellpadding=3D"2">
  <tbody>
    <tr>
      <td style=3D"text-align: left; width: 70%;"> <font class=3D"indextop"=
>Indexer
Requirements for 3.0<br>
      </font> <span class=3D"indexsub"><font class=3D"indexsub">This
document describes the proposed work items for the indexer for the CDT
3.0 release.</font></span> </td>
      <td style=3D"width: 30%;"><img
 src=3D"http://dev.eclipse.org/images/Idea.jpg"; alt=3D"" height=3D"86"
 width=3D"120"></td>
    </tr>
  </tbody>
</table>
<table>
  <tbody>
    <tr>
      <td style=3D"vertical-align: top;">Author</td>
      <td style=3D"vertical-align: top;"> : Bogdan Gheorghe<br>
      </td>
    </tr>
    <tr>
      <td>Revision Date</td>
      <td> : 11/29/2004 - Version: 0.1.0</td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top;"><br>
      </td>
      <td style=3D"vertical-align: top;">: 01/10/2005 - Version: 0.1.1<br>
      </td>
    </tr>
    <tr>
      <td>Change History</td>
      <td> : 0.1.0 - Document Creation</td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top;"><br>
      </td>
      <td style=3D"vertical-align: top;">: 0.1.1 - Revision<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<!-- End of Document Header -->
<!-- Table of Contents -->
<div class=3D"section">Table of Contents</div>
<br>
<div class=3D"indent"><a href=3D"#intro">1. Introduction</a> </div>
<div class=3D"indent"><a href=3D"#reqs">2. Requirements</a><br>
<a href=3D"#proposal">3. UI Requirements</a><br>
</div>
<div class=3D"indent"><a href=3D"#references">4. References</a>
</div>
<br>
<br>
<!-- End of Table of Contents -->
<!-- Introduction -->
<div class=3D"section"><a name=3D"intro"> 1. Introduction</a></div>
<p>The Indexer has been around since CDT 1.2 and currently provides
support for Search, Navigation, and Refactoring. Its main purpose is to
provide rapid access to a complete database of code elements and to
manage this database in an efficient and non-intrusive manner. As the
CDT has evolved; so has the indexer - adding more elements to the
index, refining job scheduling, providing feedback mechanisms for
indexes. Although the indexer is sufficiently developed to provide most
requested information to clients; it has become clear that the next
step in the indexer's evolution will have to address its ability to
handle very large projects efficiently.</p>
<p>Having the indexer work well on large scale projects requires some
new architecture to reduce the amount of time spent indexing as much as
possible, reuse existing indexes as much as possible and provide users
with mechanisms to extend the index framework.<br>
</p>
<p>This document will address main requirements on the indexer for CDT
3.0.<br>
</p>
<h2>1.0 Definitions</h2>
<table style=3D"text-align: left; width: 100%;" border=3D"1" cellpadding=3D=
"2"
 cellspacing=3D"2">
  <tbody>
    <tr>
      <td style=3D"vertical-align: top; width: 80pt;">Resource<br>
      </td>
      <td style=3D"vertical-align: top;">A project, folder or file within
the Eclipse workspace<br>
      </td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top;">Index profiles<br>
      </td>
      <td style=3D"vertical-align: top;">Separate indexes that are
created for different configurations of include paths/symbols<samp></samp><=
samp></samp><br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<br>
<h2>1.1 Current Architecture</h2>
Quick overview of the indexing architecture:<br>
<br>
<ol>
  <li>The indexer responds to resource events from the workbench. These
events occur whenever a resource gets created, modified or deleted.</li>
  <li>The indexer will create index jobs based on the resource events.
These jobs might schedule other jobs (such as in the case of indexing
an entire project) but most index jobs eventually boil down to an
AddCompilationUnitToIndex job.</li>
  <li>The indexer creates a new parser, passes in the current include
paths and symbol definitions and parses the file and any other files
included by the file in full parse mode (which generates cross
reference information).</li>
  <li>The index gets created as the parser returns information about
the elements in the file - the index is stored in memory and at certain
intervals gets merged with the persisted index on disk.</li>
</ol>
<br>
Currently the indexes have the following structure:<br>
<br>
<ul>
  <li>Index Version Number <br>
  </li>
  <li>Summary Block Location</li>
  <li>File Blocks [1 ... N]:</li>
  <ul>
    <li>Each full file block is 8k</li>
    <li>File block entries associate the path of a file with a unique ID</l=
i>
  </ul>
  <li>Word Blocks [1 ... N]:</li>
  <ul>
    <li>Each full word block is 8k</li>
    <li>Word block entries encode the element in a special format and
add the referring file number</li>
  </ul>
  <li>Include Blocks [1 ... N]:</li>
  <ul>
    <li>Each full include block is 8k</li>
    <li>Include block entries associate a file with the initial file
that was parsed to get to the current file<br>
    </li>
  </ul>
  <li>Summary Block:</li>
  <ul>
    <li>Keeps track of the total number of words, files and include
entries in the index</li>
    <li>Keeps track of the first file block number, the first word
block number and the first include block number</li>
    <li>Keeps track of the first file for every File Block, the first
word entry for every Word Block, and the first include for every
Include Block<br>
    </li>
  </ul>
</ul>
<p></p>
<h2>1.1 Constraints</h2>
<table style=3D"text-align: left; width: 100%;" border=3D"1" cellpadding=3D=
"2"
 cellspacing=3D"2">
  <tbody>
    <tr>
      <td style=3D"vertical-align: top; text-align: left; width: 35pt;">Num=
ber<br>
      </td>
      <td style=3D"vertical-align: top;">Description<br>
      </td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">C1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Multiple
indexer profiles not possible until similar build configuration notion
appears</span><br>
      <br>
In order to get an accurate index the indexer depends on being able to
pass on the relevant includes/symbols to the parser.&nbsp; As long as
there is no standard representation for build configurations in the
core model for all build
types (both standard and managed), it isn't possible to enable index
profiles.<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D25682";>B=
ug
25682: Indexer Profiles</a><br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<div class=3D"section"><a name=3D"reqs"> 2. Requirements</a><br>
</div>
<p>List of requirements for the indexer is classified into following
categories:
</p>
<p>
</p>
<h2>2.1 Index Management Requirements<br>
</h2>
<table style=3D"text-align: left; width: 100%;" border=3D"1" cellpadding=3D=
"2"
 cellspacing=3D"2">
  <tbody>
    <tr>
      <td style=3D"vertical-align: top; text-align: left; width: 35pt;">Num=
ber<br>
      </td>
      <td style=3D"vertical-align: top; width: 35pt;">Priority<br>
      </td>
      <td style=3D"vertical-align: top;">Description<br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R1<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
must provide different types of indexing services</span><span
 style=3D"font-weight: bold;"></span><br>
      <br>
It has become apparent that the one-size-fits all indexing approach
does
not meet all of our users needs. Most clients with existing legacy
projects want some form of search/navigation but some don't want the
hassle of having to wait for an entire project to index fully before
being able to use search/navigation. Thus, in order to accommodate both
sets of user groups (those who are willing to wait for a full index to
complete and those who just want the absolute bare minimum index) we
need to offer the following indexer options:<br>
      <br>
      <ol>
        <li>Full Index: this is the "regular" index mode which uses the
CDT parser (include paths and symbol definitions need to be setup
properly); everything
gets indexed</li>
        <li>Quick Index with no setup: this will result in a "best
effort" bare bones index that should enable some navigation/search<br>
        </li>
      </ol>
      <br>
These indexer options are per project - so it is possible to have
different indexers for different projects.<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D69078";>B=
ug
69078: C/C++ indexer too slow</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R2<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexes
should be shareable between team members</span><br>
      <br>
As part of streamlining the indexing process for large projects,
indexes should be able to be shared between users working on the same
project. All index entries should make use of path variables in order
to allow indexes to be translated into different workspace locations.
(See<span style=3D"font-style: italic;"> Scanner Config Correctness
Enhancement FDS</span> for more details about path variables)<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D79661";>B=
ug
79661: All Index Entries should make use of Path Variables</a><br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D79518";>B=
ug
79518: Path/Variable Manager support service in the core(string
substitution)</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R3<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
should be able to index a project offline<br>
      <br>
      </span>For features that require a complete index it would be
ideal to have the index be created somewhere separately and imported in
at a later date. This is especially true for medium to large projects
that need a long time to index. <br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D74433";>B=
ug
74433: Offline Indexing/Index Hierarchy</a><br>
      <span style=3D"font-weight: bold;"></span></td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R4<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
should be able to merge indexes <br>
      <br>
      </span>With all of the new options for indexing, it is
conceivable that any project might have several sources to look at for
a single index. The indexer should be able to merge new index
information into an existing index (through a user action), provided
that both index formats are alike.<br>
      <br>
      <span style=3D"font-weight: bold;"> </span><a
 href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D52126";>Bug 52126:
Indexer should maintain per project indices</a><br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D74433";>B=
ug
74433: Offline Indexing/Index Hierarchy</a><br>
      <span style=3D"font-weight: bold;"></span></td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R5<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P2<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
should allow user to specify indexer settings </span><br>
      <br>
Currently the indexer uses the same settings for all projects. This
might not suit all users. Indexer settings that should be customizable
include:<br>
      <br>
      <ul>
        <li>Indexing policy: (default normal)<br>
        </li>
        <ul>
          <li>normal (always up to date)</li>
          <li>manual (index only when manually requested)</li>
          <li>static (don't update current index)</li>
          <li>after build (don't index until build)<br>
          </li>
        </ul>
      </ul>
      <ul>
        <li>Index Progress Bar displayed: (Checkbox, default displayed)</li>
      </ul>
      <ul>
        <li>Indexer default setting for new projects:<br>
        </li>
        <ul>
          <li>Currently the indexer is always on when creating a new
project. This should be changed to allow users to set the default index
behaviour when creating a new project</li>
        </ul>
      </ul>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D75884";>B=
ug
75884: Allow C/C++ Indexing to be set on or off as a default setting</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R6<b=
r>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Index
Manager must improve job scheduling smarts</span><br>
      <br>
The indexer currently has limited smarts when it comes to job
scheduling; it will prevent the same job from being queued up. But
there are other circumstances when being more aware of what's in the
job queue would solve numerous problems: including the ever recurring
double index, and source folder changes. Essentially, more information
needs to be added to individual job requests about the event that
created the job in order to enable the index manager to make smart
choices about how to best schedule the jobs. <br>
      <br>
The index manager should also run at the minimum priority.<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D60084";>B=
ug
60084: Indexer should reduce its priority when running in background</a><br>
      </td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">R7</span><br>
      </td>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">P1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
must try to keep as much as possible from all failed index attempts<br>
      <br>
      </span>The indexer needs to persist a list of all files that are
to be indexed as part of an index job. As each merge happens, the list
is updated. In the event of a crash, all work that has been merged to
disk<span style=3D"font-weight: bold;"><span style=3D"font-weight: bold;"><=
span
 style=3D"font-weight: bold;"> </span></span></span>shall be considered
as sane and the indexer will restart on the remaining files on the next
startup. <span style=3D"font-weight: bold;"><br>
      </span><a
 href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D62366";><br>
Bug 62366: [Index] Need ability to read a partial index and resume</a><span
 style=3D"font-weight: bold;"><br>
      </span></td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">R8</span><br>
      </td>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">P1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
needs to deal with new path/symbol addition/deletion gracefully<br>
      <br>
      </span>The indexer currently reindexes the entire project on the
addition/deletion of each new path/symbol. With the new per-file
scanner settings, we should only index the range of files that are
affected. (See<span style=3D"font-style: italic;"> Scanner Config
Correctness Enhancement FDS</span> for more details about per file
scanner settings).<br>
      <br>
      <span style=3D"font-size: 12pt; font-family: &quot;Times New Roman&qu=
ot;;"></span></td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R9<b=
r>
      </td>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">P1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
needs to handle Source Folder changes gracefully</span><br>
      <br>
The indexer currently does a brute force reindex of whenever anything
changes in the source folder view. This needs to change to a more
scalable solution.<br>
      <br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R10<=
br>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P4<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Resources
can be added manually to the index</span><br>
      <br>
Users can request a new index on any resource in the workspace
(including files that are included from external directories) by
selecting one or more files and choosing the appropriate option
from the context menu.<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D71821";>B=
ug
71821: Action on the indexer to parse file/folder</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R11<=
br>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P2<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>FileType
changes should trigger indexes</span><br>
      <br>
Changing the file type settings on a project might introduce new file
types as extensions that have not been indexed as of yet. The indexer
should react in accordance to the users settings (as defined in R5).<br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D72396";><=
br>
Bug 72396: The indexer is not aware of the File Type (ResolverModel)</a><br>
      </td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">R12</span><br>
      </td>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">P1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
Extension point</span><br>
      <br>
If all the current versions of the indexer don't meet the users
requirements, the CDT should provide an extension point that will allow
users to write their own indexer that will populate the index. Provided
the information is complete, all index-based CDT features should work
as normal.<br>
      <br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R13<=
br>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P4<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Index
Manager should allow for ongoing search while indexing</span> <br>
      <br>
The indexer should be able to compare incoming index entries with
any pending search queries and return the matches. <br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D72803";>B=
ug
72803: [Performance][Usability][Indexer/Search] Waiting policy for
index results</a><br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D53792";>B=
ug
53792: [Scalability] Prioritizing the indexing when searching a working
set</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">R14<=
br>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Index
should provide an interface to allow clients to determine what features
are available with the current indexes</span><br>
      <br>
With the prospect of having various levels of detail available in a
project's indexes, the Index Manager needs to be able to provide an
interface that will answer any client whether there is sufficient
information in the index to run the client's service. If the necessary
index detail is missing, it would be up to the client to ask the user
if they wish to schedule a new index.<br>
      <br>
      </td>
    </tr>
  </tbody>
</table>
<h2>2.2 Index Content Requirements<br>
</h2>
<table style=3D"text-align: left; width: 100%;" border=3D"1" cellpadding=3D=
"2"
 cellspacing=3D"2">
  <tbody>
    <tr>
      <td style=3D"vertical-align: top; text-align: left; width: 35pt;">Num=
ber<br>
      </td>
      <td style=3D"vertical-align: top; width: 35pt;">Priority<br>
      </td>
      <td style=3D"vertical-align: top;">Description<br>
      </td>
    </tr>
    <tr>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">R15</span><br>
      </td>
      <td style=3D"vertical-align: top; text-align: center;"><span
 style=3D"font-weight: bold;">P1</span><br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
will provide enough information to run searches without a second parse<br>
      </span><br>
Currently the index stores just the location information for the
entries - this currently causes search to require two separate parses:
one for the initial index and another to determine the offset
information. The indexer should store this offset information in the
initial index and thus avoid the second parse. Enough information must
be available in the index to answer all of the possible MatchLocator
queries. Additional info that needs to be added to the indexer includes:<br>
      <ul>
        <li>function/method parameters</li>
        <li>if a variable has an initializer clause, extern specifier
or linkage specification (needed to determine if it is a definition)</li>
        <li>if a field is static (needed&nbsp; to see if we need to
check for definition)</li>
      </ul>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D74427";>B=
ug
74427: Indexer needs to store more info</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R16<=
br>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P3<b=
r>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>References
in the index should be tied into their declarations</span><br>
      <br>
We need to be able to match up references to their declarations
(possible requirement for refactoring support).<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D69606";>B=
ug
69606: [Search] Match locator has to make sure that the reference
belongs to the specified declaration</a><br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">R17<=
br>
      </td>
      <td
 style=3D"vertical-align: top; text-align: center; font-weight: bold;">P1<b=
r>
      </td>
      <td style=3D"vertical-align: top; font-weight: bold;">New Indexer
needs to be written for new AST<br>
      <br style=3D"font-weight: normal;">
      <span style=3D"font-weight: normal;">As the CDT switches over to
the new AST, the indexer will have to be rewritten to extract
information from the AST.</span><br>
      </td>
    </tr>
  </tbody>
</table>
<span style=3D"font-weight: bold;"></span>
<ul>
</ul>
<br>
<h2>2.3 Problem Markers<br>
</h2>
<br>
<table cellspacing=3D"2" cellpadding=3D"2" border=3D"1"
 style=3D"text-align: left; width: 100%;">
  <tbody>
    <tr>
      <td style=3D"vertical-align: top; text-align: left; width: 35pt;">Num=
ber<br>
      </td>
      <td style=3D"vertical-align: top; width: 35pt;">Priority<br>
      </td>
      <td style=3D"vertical-align: top;">Description<br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">&nbs=
p;R18<br>
      </td>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">&nbs=
p;P2<br>
      </td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Problem
Markers should be able to be removed manually<br>
      <br>
      </span>There are a number scenarios in which Index problem
markers get placed on resources and cannot be removed. There needs to
be some sort of menu option that can manually delete selected problem
markers.<br>
      <br>
      <a href=3D"https://bugs.eclipse.org/bugs/show=5Fbug.cgi?id=3D74284";>B=
ug
74284: [IProblem] All Problem markers removed for project when one file
is excluded</a><br>
      <span style=3D"font-weight: bold;"></span></td>
    </tr>
  </tbody>
</table>
<span style=3D"font-weight: bold;"></span>
<ul>
</ul>
<p><!-- End of Introduction --><!-- References -->
</p>
<div class=3D"section"><a name=3D"proposal"> 3. UI Requirements</a><br>
</div>
<br>
<h2>3.1 UI enhancements</h2>
Following UI enhancements are planned to support the feature:<br>
<br>
<table style=3D"text-align: left; width: 100%;" border=3D"1" cellpadding=3D=
"2"
 cellspacing=3D"2">
  <tbody>
    <tr>
      <td style=3D"width: 35px; vertical-align: top;">Number<br>
      </td>
      <td colspan=3D"1" rowspan=3D"1" style=3D"vertical-align: top;">Descri=
ption<br>
      </td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">UE1<=
/td>
      <td style=3D"vertical-align: top;"><span style=3D"font-weight: bold;"=
>Indexer
Options Preference Page<br>
      <br>
      </span>This page will allow users to make changes to the Indexer
that affect the entire workspace:<span style=3D"font-weight: bold;"><br>
      </span><br>
      <ul>
        <li>Index Progress Bar displayed</li>
        <li>Indexer New Project Default Setting<br>
        </li>
      </ul>
      <span style=3D"font-weight: bold;"></span></td>
    </tr>
    <tr>
      <td
 style=3D"vertical-align: top; font-weight: bold; text-align: center;">UE2<=
br>
      </td>
      <td style=3D"vertical-align: top; font-weight: bold;">Indexer
Project Properties Page<br>
      <br>
      <span style=3D"font-weight: normal;">This page will allow users to
set indexer settings per project:</span><br style=3D"font-weight: normal;">
      <ul style=3D"font-weight: normal;">
        <li>Indexer to use: if a number of indexers are available (ie.
SourceIndexer, SourceIndexer2, CTagsIndexer) , users can specify which
indexer should be used for the entire workspace.</li>
        <li>Indexing policy to use</li>
      </ul>
      <br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<div class=3D"section"><a name=3D"references"> 4. References</a> <br>
</div>
<br>
<ol>
  <li> Scanner Config Correctness Enhancement FDS </li>
</ol>
<p>
<table border=3D"0" cellpadding=3D"2" width=3D"100%">
  <tbody>
    <tr>
      <td colspan=3D"2" align=3D"left" bgcolor=3D"#0080c0" valign=3D"top"><=
br>
      </td>
    </tr>
  </tbody>
</table>
</p>
<center><i>Last Modified on Monday, January 10, 2005
</i></center>
</body>
</html>
--=_mixed 00764EAB85256F88_=--


--__--__--

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


End of cdt-dev Digest



Back to the top