Given an intended market of C++ programmers, is Felix being taught in the wrong order?
The current approach is: it's an standalone language with it's own types and semantics, and the C++ binding details are are introduced afterwards to show how to roll your own semantics. Would it be better to reverse this top down approach for the C++ market and show how to use Felix "as C++" and gradually introduce more abstraction? For example: header, body statements type primitives fun, proc primitives cfun, cproc (yay! Actual Felix!) export .. etc Furthermore, if Felix is improved in this area so that it can be used simply to link existing C++ projects .. we have the start of the seamless transition needed to get a foothold in the market. Just using flx script, leveraging flx_pkgconfig for dependencies is already a fairly major improvement for many C++ programmers. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
