[Fwd: v.target() does not work properly (fwd)]

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Fwd: v.target() does not work properly (fwd)]

Tiago de Paula Peixoto
-------- Original Message --------
Subject: v.target() does not work properly (fwd)
Date: Thu, 1 Mar 2007 11:18:51 +0100 (CET)
From: Marodi Mate <[hidden email]>
To: [hidden email]
CC: [hidden email]

[I try again...]

(neither does v.source())

if one applies the example about the number of second neighbors in the
manula,
the result is, of course, the one put there. Unfortunately it is not
correct:
only one node has 2 2nd neighbors.
the problem is seemingly with n.target() in edit_function(). every time it
returns a vertex, it returns a completely new one. the same is true for
n.source().

Mate Marodi

--
Tiago de Paula Peixoto <[hidden email]>

Reply | Threaded
Open this post in threaded view
|

Re: [Fwd: v.target() does not work properly (fwd)]

Tiago de Paula Peixoto
On 03/01/2007 07:45 PM, Tiago de Paula Peixoto wrote:

> -------- Original Message --------
> Subject: v.target() does not work properly (fwd)
> Date: Thu, 1 Mar 2007 11:18:51 +0100 (CET)
> From: Marodi Mate <[hidden email]>
> To: [hidden email]
> CC: [hidden email]
>
> [I try again...]
>
> (neither does v.source())
>
> if one applies the example about the number of second neighbors in the
> manula,
> the result is, of course, the one put there. Unfortunately it is not
> correct:
> only one node has 2 2nd neighbors.
> the problem is seemingly with n.target() in edit_function(). every time it
> returns a vertex, it returns a completely new one. the same is true for
> n.source().
>
> Mate Marodi
>

Yes, you're correct... I forgot to add the __eq__ and __hash__ member
functions to the Vertex and Edge classes, so they could be compared.
This is fixed in svn now, and I also updated the documentation. Thanks a
lot for the bug report.

I also detected the problem which prevented you from posting to the
list, and I think it's fixed now.

Cheers.
--
Tiago de Paula Peixoto <[hidden email]>