On Wed, Apr 08, 2009 at 19:28:06 +0200, Mads Lindstrøm wrote: > I link to Huber's langauge-c > http://hackage.haskell.org/cgi-bin/hackage-scripts/package/language-c > for those who want to check it out. > > Anyway, can we do with a C parser? Won't we need a C++ parser?
I guess that depends if those header files in wxWidgets happen to be C parseable. Anyway, it's not that great a priority. I was just looking at various ways we could chip away at the wxhaskell build method and make cabal installing wxhaskell smoother. This doesn't play too great a role in it. But getting rid of this Eiffel stuff does make wxHaskell a little less random looking, which could be handy if we want to explain to outsiders what's going on later. I wish we could convince wxWidgets HQ to take care of wxc. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com
_______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
