Re: [Getfem-users] Commit 4120

[Andriy Andreykiv]

Dear Kostas,

I think this was me who implemented copy constructor for mesh_fem
recently and "privatized" operator=.
The reason is that there was no copy constructor before, so the copy
operation was generated by the compiler
and it wasn't done correctly. I made the operator "=" private to point
out that if it's not, the default operator might
behave not the way you expect.

You can have two solutions here: 1)quick and dirty one - remove my
private declarations. Expect problems when
you copy one mesh_fem to the other and one of them is local variable
that goes out of scope, while the other is global (the global one will
get unvalid context)
2)The thorough solution (but still as quick as this email :) ) is to
still make operator "=" public but define it similarly to the copy
constructor.

Best regards,
                        Andriy


On 25 July 2012 13:18, logari81 <address@hidden> wrote:
> Hi,
>
> I have some issues with the change introduced in revision 4120. Making the =
> operator for the mesh_fem class private, will not let you resize or fill a
> std::vector<getfem::mesh_fem> because the copy operator is required.
>
>
> Is it possible to rework this commit so that it doesn't cause this
> restriction?
>
> Best regards
>
> Kostas
>
>
> _______________________________________________
> Getfem-users mailing list
> address@hidden
> https://mail.gna.org/listinfo/getfem-users