While doing exercises with Forth - using DX-Forth (
http://www.netbay.com.au/~dxforth/ ) - I noticed, that its "ms" word
delays _exactly twice_ the given number of milliseconds.
Several tries revealed, that this word works correctly only when both
XMGR memory manager is used (not JEMMEX, for instance), and as a shell
command.com is chosen, not 4DOS. It's enough not to fulfil one of
these conditions, and again the delay is two times longer, than
expected.
Any ideas, what actually can be wrong? And should it be corrected in
JEMMEX/4DOS - or in DX-Forth rather?
If I correctly found the relevant sections of DX-Forth's kernel.asm
(it's included in the package), the word is defined the following way:
#v+
[..]
; runtime for deferred words - equiv to @ EXECUTE
dodef: pop bx
jmp [bx]
[..]
; MS ( ms -- )
hdr 1,'MS'
ms: call dodef
dw ms0
;
[..]
#v-
--
regards,
Zbigniew
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
