Scripting Questions:
-
Category: News ArchiveHits: 1064
Hopefully you will include at least a mechanism to write the current time (to the millisecond?) to the log files.
Perhaps also a current "free memory" if available.
This will allow us to profile some aspects of the scripting engine.
It would be awfully nice to know what kind of overhead different looping constructs require, how long it takes to set a global variable, is "sleep"ing available? Is it less intensive than setting up a time-trigger? etc.
Anything you can do to give us some details on how to best optimize our scripting would be wonderful -- not NOW -- just when released. :-)
- "Free memory" is usually a fiction in most programs, since the way that memory is allocated and deallocated can cause memory fragmentation ... leading you to believe that you have a lot more memory than you actually have. What's the point of knowing that you have 40 MB free if it can only be allocated in 16 byte chunks?
Having said that, the total amount of memory allocated might not be a bad thing to know ... we'll look into exposing that.
We already have a logging function that allows the end user to write the current date/time in "world time" to the log, and it would actually be fairly trivial to convert it to one that also write out the system time stamp instead.
--
Mark Brockington
