Hi, I moved the monotonic counter code to the VM and adapted the threads vocabulary to use it. The reason for moving to the VM is so that threads works with the non-optimizing compiler. Previously, we had a VM primitive 'micros' and a utility word 'millis', which returned system time, and the library word monotonic-count, which returned a nanosecond count from an arbitrary offset.
In order to make it more clear to the user if they're getting system time or some arbitrary count of incrementing nanoseconds, I renamed a few words: millis -> system-millis micros -> system-micros monotonic-count -> nano-count Now it should be apparent which words are useful in which situations -- system-millis and system-micros for obtaining system time for date calculations, and nano-count for timing and profiling. One benefit of moving to monotonic timers is that Factor no longer hangs when you set your system clock ahead, as it used to when timers were based off system time. I should have fixed this problem much sooner. Doug ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
