On Jul 15, 2004, at 6:34 AM, Tal Cohen wrote:
With regards to portability, it is OK if I end up writing different code for different machines (BAD Tal, BAD!!!). However I do want to keep it as light weight and internal as possible.
If you can't use an external infrastructure like SNMP, then you are probably best off using the earlier suggestion to put the system specific code in separate modules and have them provide a common interface. Then you have one module that you can ask for one of these memory reporting objects and it hands back the correct, system specific one. (Perhaps determined via some sort of system configuration, perhaps with code that will probe the system and find the most appropriate one.)
Which operating systems do you need to deploy on, initially? We have given a variety of solutions so far for Linux, Windows, Mac OS X, MS-DOS, and recent BSDs. For other Unix systems, I thought of one additional method. You might be able to open /dev/mem, seek to the end, and then use tell() to report its position.
"When I write 'Barbie', am I supposed to add the little R in a circle around it?"" -- Samantha Langmead, age 7.
"When I write 'Barbie', am I supposed to add the little R in a circle around it?"" -- Samantha Langmead, age 7.
_______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
