dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Thu, Sep 29, 2005 at 06:20:16PM +0200, Johan Jansson wrote:
> On Thu, Sep 29, 2005 at 11:15:44AM -0500, Anders Logg wrote:
> 
> ..,
> 
> > > One problem we need to solve is that SWIG doesn't support nested
> > > classes. Perhaps we can come up with an alternative? I don't think
> > > they're crucial for us.
> > 
> > You mean don't use nested classes in DOLFIN?
> > 
> > Can we still have private nested classes that are not exposed in the
> > interface?
> 
> Hm, I didn't consider that. This may not be an issue then, since I
> don't think we use nested classes in the public interface (as far as I
> know). I'll have to test this, but my guess is that the answer is yes
> to your question.

One place where we have public nested classes is in the code generated
by FFC:

class BilinearForm : public dolfin::BilinearForm
{
public:
    
  class TestElement : public dolfin:FiniteElement
  {

  }

  class TrialElement : public dolfin::FiniteElement
  {

  }

}

If necessary, we could think of reorganizing this.

Can SWIG do nested namespaces (as opposed to nested classes)?

/Anders