skaller wrote: > Well, I am inclined to release 1.1.3 final soon. I have asked > Mike to package 1.1.3_rc4 but so we do a final test on > the debian autobuilder, however no response so far. > > I don't think we can wait for a perfect (bugless) system. > I'm inclinded to release so we can move on. > > Comments? >
I'm fine cutting a new release. What do you think about changing the version numbering though? The standard approach is major-minor-bug fixes, and I think typeclasses are important enough to bump up the minor version. To give us some room though, maybe it should be 1.02.00 so that we can grow beyond 1.9 if we need to. > And what should we move on TO? > Oh lots of stuff that should be going into http://code.felix-lang.org :) One smallish thing I'd like to see is that we really do have a ton of keywords, and I don't think all of them are really used. I think we may have 2-3 times as many keywords as the other major languages. Perhaps we could eliminate some. I'd also like to finish the transition over to felix-lang.org and google groups. A fast cgi implementation would be nice. Replacing the macro "print" with a "proc print[T with Show[T]] (x:T) ...", as well as getting "f'int: %s float: %s' (1, 5.0)" to work. Figuring out a way to map builtin compiler types (like case 5 of 7) to user defined ones without using macros so that something like the builtin regexp can effectively return opt[T], along with somehow pretty printing errors when a type doesn't match. Or go completely crazy and just pull the types directly into the compiler. That may be too ambitious though. Unify streams, schannels and pchannels. Start migrating datatype algorithms, regexp, reglex, and parse to support streams. Flesh out the unicode support so that the string functions can be used on them. Make a String typeclass so that strings, ustrings, and wstrings don't have to keep reimplementing the same functions. Come up with a generic python/haskell-like list comprehension sugar. Figure out how to do the mythical list/hash table creation sugar. User defined pattern matching. Rename system calls from _svc to __svc_, and _ctor_int to __ctor_int, or something else to make it a little more unique. Lots of projects use _foo for user-level internal functions. Come up with a standard for c++ style import/include guards. Analyze the language "D" from http://www.digitalmars.com/d/index.html to see if there's anything interesting to steal :) they seem to have a similar syntax, so there may be some stuff to borrow. They do a lot of stuff to make it easier to engineer projects like scope guards (http://www.digitalmars.com/d/statement.html#ScopeGuardStatement). Surely that's more than we'd want to have for the next release :) What do you have in mind? -e ------------------------------------------------------------------------- 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
