Java Universal Network/Graph Framework

Tracker: Bugs

5 Context<G,E> or DefaultParallelEdgeIndexFunction<V,E> bug - ID: 2887196

Last Update: Comment added ( e-flat )

Details:

When two not equal edges e1 and e2 have identical hash codes, their
Parallel Edge Indices are the same, but should be different. The problem is
that when Context of e2 is put into Map<Context<Graph<V,E>,E>, Integer>
edge_index, where Context of e1 is already present, it replaces Context of
e1, because the Contexts' hash codes and references are the same.

Submitted:

Sasha Kazachonak ( ) - 2009-10-27 14:11

Priority:

Status:

Open

Resolution:

None

Assigned:

Nobody/Anonymous

Category:

Core Graph Code

Group:

Possible Bug

Visibility:

Public

Comment ( 1 )

Date: 2009-10-27 16:03 Sender: e-flat Sasha: I assume you're aware that having non-equal objects with identical hash codes can cause problems; is this a deliberate choice on your part, chance, or an emergent property that you have no control over? Context.equals() is defined in such a way that this should not be an issue. Can you provide a minimal self-contained test case that demonstrates this behavior? Joshua

Date: 2009-10-27 16:03
Sender: e-flat

Sasha:

I assume you're aware that having non-equal objects with identical hash
codes can cause problems; is this a deliberate choice on your part, chance,
or an emergent property that you have no control over?

Context.equals() is defined in such a way that this should not be an
issue. Can you provide a minimal self-contained test case that
demonstrates this behavior?

Joshua

Log in to comment.

Attached File

Change ( 1 )

Field	Old Value	Date	By
artifact_group_id	Verified Bug	2009-10-27 16:03	e-flat

Java Universal Network/Graph Framework

Tracker: Bugs

Comment ( 1 )

Log in to comment.

Attached File

No Files Currently Attached

Change ( 1 )

About SourceForge

Find Software

Develop Software

Community

Help