On Mon, Mar 30, 2009 at 12:49 AM, john skaller <skal...@users.sourceforge.net> wrote: > Yes. It never works properly, and is impossible to maintain on multiple > platforms. > > Also, Async TCP/IP is stuffed as we found out,.. someone should write > a paper > on that and send it to some conference, it is a SERIOUS issue costing > billions > of dollars and compromising world network security.
Which bugs are you referring to? Maybe the erlang folks have some ideas on working with it. Ulf Wiger, you still subscribed? > At this time, parsing is the major problem. Before Dypgen, binding > dominated. > > We already have separate parsing (*.par files) and binding can only be > reduced, > across compilation unit binding will always be necessary. Sure, I don't think we can excape binding across files, but isn't that what all the partial compilation languages have to do? We'd somehow say that such and such functions are found here, and variables here and they have these types and etc. And then in the other module, look up the exposed values in the module and link appropriately. I can see how it'd be tricky to do this when compiling to a c text file, that's why I'd only explore this with llvm. ------------------------------------------------------------------------------ _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
