From: Xavier V. <xav...@fr...> - 2004-03-13 20:12:49
|
Hello Michael, Martin and others > - lcd4linux will stay pure C (as the linux kernel does) > - lcd4linux will not use any threading library, the places where > asynchronous execution is necessary are rare and will be solved using > traditional fork() and shmem. In fact to aswer to Martin, C++ threads are less memory-wasting than the C fork(), as fork copy the whole process, with its variable and others. I don't know what you think about it, but maybe we can fork very early in 3 threads: main, plugins, and soon input to make all these work asyncronously and solve many problems we'll encounter with input. But this will surely lead to problems with shared variables and other. Do as you want Michael, but IMHO slitting into 3 (by now 2) threads would be "proper". But we'll be able to troll about this after 0.10.0 is released. ;) > >>If you could make your Excel-Todo-Sheet up to date, this would be of > >>help here. > > First, I don't use excel !!!! > Sorry, I forgot that you already "ported" the Status list to ASCII :-) Errr ... some people use free software like OOo instead of "crossover office" ! See photo06.jpg of LinuxDay on the site, the last three icons in the KDE panel : are these word, excel and powerpoint (at least I think) icons shortcuts to OOo components ? What can you argue for your defense ? > What about plugin_wifi? Martin will neeed it, IIRC. I began to write it last week while recompiling a 2.6.3 kernel on a 133MHz notebook (so I had time to code :D ), it was a mere copy of plugin_netdev.c as the two files /proc/net/dev and /proc/net/wireless are similar, but I found a syscall to retreive the informations, so I dropped the source. I have to dig more about this function and write the plugin --> added to my ToDo :) Bye ! -- Xavier VELLO <xav...@fr...> |