On Mon, 2003-01-20 at 01:45, Alexander Demenshin wrote: > > been a _lot_ easier (as well as faster and less memory intensive). And > > since I already have most of the required library code written, there's > > not much need to use GLIB anyway :) > > Is it (your library) portable? Can it be used on Win32? To be honest, I > really dislike glib, and I like when there are no external dependencies > exists (except for standard C library and anything else which works well > on Win32 as good as on *ix) :)
My library is portable across UNIX systems. The parts that I'd use with irssi would mostly be ANSI-C. Handling sockets would be the only tricky part, there's no code for that yet. But I never got GLIB 1.2 or early 1.3 to work well with winsock either, maybe they've fixed it though. > > but I also think that irssi should be fully functioning for most people > > without external scripting language. > > Unless there will be some embedded scripting language :) I think this idea > is not bad - make everything which needs optimization in C, but everything > else in interpreted language - this will help to avoid a lot of problems > related to buffer overflows etc. "Fully functioning for most people without external scripting" is a must. Notify lists, ignores, hilights etc. are basic functionality and will be implemented with either C or internal scripting. I think most of the irssi's current functionality falls there .. not everything though.
