On Jul 6, 2011, at 1:54, Anders Logg <l...@simula.no> wrote: > I'm thinking of how to handle this bug: > > https://bugs.launchpad.net/ffc/+bug/787010 > > I see two solutions: > > 1. Handle parameters with dynamical type in C++ (fairly easy to add).
Not sure I like this. It is nice to have a strongly typed regime here. > 2. Not use parameters that may change type in FFC (from "auto" to an > int). Is it possible to store the parameter As an int internally in FFC, -1 for auto, and then add logic to the parsing of this variable so 'auto' becomes -1? Did that make sense? Johan > -- > Anders > > _______________________________________________ > Mailing list: https://launchpad.net/~dolfin > Post to : dol...@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dolfin > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~ffc Post to : ffc@lists.launchpad.net Unsubscribe : https://launchpad.net/~ffc More help : https://help.launchpad.net/ListHelp
