Linked by Eugenia Loli on Mon 27th Aug 2001 05:22 UTC
Syllable, AtheOS AtheOS is a modern, free (GPLed) Operating System written from scratch in C++. A big chunk of the OS is POSIX compliant, supports multiprocessing and it is GUI-oriented (fully OOP). Today we are hosting an interesting interview with the AtheOS creator, Kurt Skauen. Kurt is talking about his views on binary compatibility in future versions, multithreading and the future of his OS in general.
E-mail Print r 0   · Read More · 53 Comment(s)
Permalink for comment
To read all comments associated with this story, please click here.
by Joe on Fri 7th Sep 2001 02:23 UTC

Okay, my two cents?? While it is good to use MT throughout a system, I believe there should be some automation of coding... in other words: Allow programmers to program in a familiar language, but all that would be necessary for a new thread, is to create a new *.h or whatever file... I am not a C programmer, but I feel that this wouldn't be tooo bad for the developers.... If they wanted to do things in a seperate thread, just create a new file..perhaps a thread file to include in the final compilation similar to the following: # Thread File !/thread_prio=normal # set the thread's priority...can be set in any way, of course !/thread_app_id=MyApp # To link this thread inherently, and quickly to your App !/thread_id=ThreadName # To be called from other threads like: CallThread(thread_id), thread_data IF "$thread_data" == "" do/then do_null() # do_null() would be set in the compiler the same as return_app, this would be used to avoid running any more checks than needed... "$thread_data" /= "" do/then # /= is does not if the thread_data has anything in it, it will be processed do_thread_work($thread_data) #this would of course do the dirty work of the thread, defined in any variety of places... else return_app() # this causes a quick termination of the thread, without an error.. return (0) I think is similar, but this will keep it simple-in-the-head... FI :do_thread_work #could be used to define work to be done... IF $thread_data size > 32 do/then # this will be to do small work... goto_thread_id(large_work) # just making the hard work go to another thread... else do_dirty_stuff($thread_data) FI :do_dirty_stuff # again, just defining the work DO WHATEVER WORK THAT NEEDWS TO BE DONE... Do you guys get it?? And, yes, I realize that I could easily just set the main app to filter the thread_request() to the correct filter, but I feel that this could probably be done in a totally new thread, so do_dirty_work would simply be another file or sub... Pretty simple...and fast, I would think... Would anyone be interested in something like this?? OF COURSE, THIS WOULD HAVE TO BE MADE BY A PROGRAMMER... I have looked at code, but I have never written my own C code... HTML, JAVASCRIPT, BAT(CH), Q/BASIC)...but NO no jokes.... ;-) I would be VERY interested to hear what y'all have to say... Maybe this can be used to help Atheos in the future... ;-) A little tie-in would be nice...seeing that VERY FEW posts have been directly pointed towards to AtheOS. Of course, learning the down/short-falls of a GREAT OS such as BeOS during the developement phases of another, similar enough, OS could be very healthy for that OS.... Anyway..that is my $2000000000 worth...