dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #26336
Re: MeshDomain
-
To:
"Garth N. Wells" <gnw20@xxxxxxxxx>
-
From:
Johan Hake <hake.dev@xxxxxxxxx>
-
Date:
Mon, 11 Feb 2013 11:05:56 +0100
-
Cc:
dolfin@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<CAA4C66N5bXv=UDb-vCUKSbtGXF-+inVmsT9Vo8iXkXF34GFjgA@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
On 02/11/2013 10:45 AM, Garth N. Wells wrote:
> On 11 February 2013 09:39, Johan Hake <hake.dev@xxxxxxxxx> wrote:
>> While trying to add mesh to MeshDomains I get an error because the method:
>>
>> MeshDomains::mesh_function
>>
>> is static preventing me to access member data.
>>
>> Why is this method static?
>>
>
> I guess just because it could be (i.e. it doesn't access member data).
Make sense.
Johan
> Garth
>
>> Johan
>>
>> On 02/11/2013 09:00 AM, Johan Hake wrote:
>>> I am adding some functionality to MeshDomains, (actually to SubMesh,
>>> which soon also propagates MeshDomains to the new mesh), and wonder if
>>> there where any good reasons why a MeshDomain does not have a pointer to
>>> the parent mesh?
>>>
>>> If such was provided during construction we could skip the annoying mesh
>>> argument in:
>>>
>>> facets_domains = mesh.domains().facet_domains(mesh)
>>>
>>> Johan
>>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dolfin
>> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dolfin
>> More help : https://help.launchpad.net/ListHelp
References