RE: [cdt-dev] Error Parsers behavior problems?

["Treggiari, Leo" <leo.treggiari@xxxxxxxxx>]

There seems to be some desire to allow the "let CDT pick the error
parser order" behavior (Jeremiah and Alex).  In that case, I suggest
modifying the "generic" error parser picker dialog to contain an "Enable
Error Parser Ordering" check box.  If true, the Up and Down buttons
would be active at the appropriate times (as they are today), and the
error parser manager would respect the specified order.  If false, the
Up and Down buttons would be disabled and the error parser manager would
be free to re-order the error parsers.

This requires an additional attribute to be stored with the error parser
list for both Standard Make and Managed Make projects.  "Enable Error
Parser Ordering" would default to false, but could be overridden by a
Managed Make target definition, as the list of error parsers can be
today.

Comments?

Leo Treggiari
Intel Corp.


-----Original Message-----
From: cdt-dev-admin@xxxxxxxxxxx [mailto:cdt-dev-admin@xxxxxxxxxxx] On
Behalf Of Lott, Jeremiah
Sent: Tuesday, May 25, 2004 11:27 AM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Error Parsers behavior problems?

Yep.  Sorry about the mistype.  

Your suggestion about order seems reasonable.  We could use a check list
for the error parsers.  By default the list could be in the order that
CDT calculates.  There could be an "Order..." button which would launch
a separate dialog for the user to manually override the order.

Just a thought.  I'll let people more familiar with this subsystem
comment from here on out.

  Jeremiah Lott
  TimeSys Corporation


-----Original Message-----
From: Alex Chapiro [mailto:achapiro@xxxxxxx] 
Sent: Tuesday, May 25, 2004 11:30 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Error Parsers behavior problems?


I didn't find this class in JDK 1.4.2 :-) Probably you meant
LinkedHashMap?

Returning to the third point. Maybe this option should be saved for lazy

users as a check box on the error parsers page to let them check it in 
preferences and do not set order for every new project, just rely on the

order CDT calculates.

Lott, Jeremiah wrote:

>A quick fix to the HashTable problem might be to use LinkedHashTable, 
>which behaves as a HashTable, but also maintains insertion order (via 
>an internal linked list).  I didn't look at the code, but from the 
>newsgroup it seems that this would help.
>
>  Jeremiah Lott
>  TimeSys Corporation
>
>-----Original Message-----
>From: Alex Chapiro [mailto:achapiro@xxxxxxx]
>Sent: Tuesday, May 25, 2004 9:49 AM
>To: cdt-dev@xxxxxxxxxxx
>Subject: Re: [cdt-dev] Error Parsers behavior problems?
>
>
>
>
>Treggiari, Leo wrote:
>
>  
>
>>I have the following comments:
>>
>>
>>
>>1.  The fact that error parsers are not invoked in the order specified
>>by the user
>>
>>   seems like a bug that should be fixed.
>>
>> 
>>
>>    
>>
> From JDK 1.4 documentation:
>
>The Map interface provides three /collection views/, which allow a 
>map's
>
>contents to be viewed as a set of keys, collection of values, or set of
>key-value mappings. The /order/ of a map is defined as the order in 
>which the iterators on the map's collection views return their
elements.
>
>Some map implementations, like the TreeMap class, make specific
>guarantees as to their order; others, like the HashMap class, do not.
>
>So your conclusion is eventually correct 
>_______________________________________________
>cdt-dev mailing list
>cdt-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>  
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev