[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Getfem-users] Namespace problem with mesh_precomposite and composit
From: |
Yves Renard |
Subject: |
Re: [Getfem-users] Namespace problem with mesh_precomposite and composite_approx_int_method() |
Date: |
Mon, 10 Aug 2015 19:45:33 +0200 (CEST) |
Dear Torquil,
You are right, this is more correct. I apply your changes to
getfem_integration.h.
Thank you,
Yves.
----- Original Message -----
From: "Torquil Macdonald Sørensen" <address@hidden>
To: "getfem-users" <address@hidden>
Sent: Tuesday, August 4, 2015 4:04:24 PM
Subject: [Getfem-users] Namespace problem with mesh_precomposite and
composite_approx_int_method()
Hi!
While implementing my own mesh_fem and mesh_im, I tried to use
getfem::composite_approx_int_method()
but it exects to be passed a
const getfem::mesh_precomposite&
as its first argument. However, mesh_precomposite is not in getfem::,
but in bgeot::. So I got the following error message:
error: invalid initialization of reference of type ‘const
getfem::mesh_precomposite&’ from expression of type ‘const
bgeot::mesh_precomposite’
I was able to fix this by changing three things in
src/getfem/getfem_integration.h
1) Add #include "getfem/bgeot_poly_composite.h" near the top
2) Comment out "class mesh_precomposite;" on line 326
3) Change to "const bgeot::mesh_precomposite &mp" as the first argument
in the function prototype on line 328.
Now my program compiles fine, because I can declare a
bgeot::mesh_precomposite which I pass to
getfem::composite_approx_int_method(). My other getfem-programs still
work properly as well.
Is this something that can be included in getfem?
Best regards,
Torquil Sørensen
_______________________________________________
Getfem-users mailing list
address@hidden
https://mail.gna.org/listinfo/getfem-users