Call sys poll
I have decided to use only one call sys for DexOS, which would you chose and why ?

I voted for INT's, you can't say that they are slow on a 2.0 ghz! :wink: But to support both is a good idea, so why not?

Two call sys are easy to do but, i like to simplify things, if we use one method people will get used to using that method.

I voted for the call table. Although as pointed out INT's are not exactly slow on a 2GHz CPU they aren't the quickest method either. In general I think things done often should be optimised for speed and you should compensate by optimising other things for size. Calls (Especially memory allocation) will happen alot.

I also voted for call tables, as that's been my preference all along...

I wonder who voted for "I do not mined which"? ....incaseyoudidn'tknowitwasmeihavenoknowlegeofcallorint. Jas2o

I vote for INT perahps the SO only inform the hardware, not operate the device...but I not sure... the use of CALL TABLE waste 1 reg (eax) for select func, beter if eax is a parameter

A call table is better IMO. Wouldn't the CPU benefit from frequently used subroutines in the L2/3 cache? (Correct me if I'm wrong :p)

In case people new to Dex4U, may read this topic, i would like to point out that Dex4u has both call table and int, so you can choose the one that sutes you. As for me, i find that some times, call table is best and other times int's is best, i use mostly call table from programs, but int's from modules.

Hey, this was my poll! :D http://www.osdev.org/phpBB2/viewtopic.php?t=14109 I've never heard of DexOS's 2nd forum when I was writing that article, what a coincidence :shock: Also I wanted to add in my OS selection between pmode disk drivers and BIOS disk drivers, and before I could make that in my OS, voila, its in DexOS new version... lol Dex you are a mind reader :lol:

I agree great minds think alike ;). This is our first forum, it served us well for years. How is your OS coming on ? .

Well, my OS is halted due to school takin' place... :( Developers wanted! :D