On 17 December 2010 23:11, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
Packages would be nice, but I think a more important goal is to get the vm to describe error conditions. Â If it did that reliably, I would have been completely content to unzip a binary and write a shell script, or just use a one-click image. Â Of the things that are under reported, the most notable is when a shared library does not load, where did the vm look for it? Â One gives it a name via #moduleName, but the vm modifies it and then tries to load using the result. Â If it fails, it needs to say where it looked. Â What was the error code?
This problem lies in different plane: improving the VM code for error reporting. But first we need to build VM. Once we have it, we can play with various options, configurations, settings and so on. And then like biologists, we can afford simply put a dozens of various micro-cultures into incubator (vm configs into build server) and come back next day and see which culture having higher chances to survive (faster, less red tests and error reports) :)
Bill
-- Best regards, Igor Stasenko AKA sig.