Modula2 packages
11 messages in this thread
Richie – I just read your Benchmark review. I thought it was
very informative. I have the package on order right now
and am anxious to give it a try myself.
Is it possible to disable the Benchmark startup code and
just use your own startup PROCEDURE?
Mike 70030,160
Mike–
I use Benchmark from CLI rather than from the boot disk they supply. You
have to assign m2l to the cd where they are to be found.
// Jim
As far as I know, you can't disable the startup code. However, it's possible
to close the annoying window that is open automatically for you…Richie
Richie, Thats like holding a bone in front of a hungry dog, just out of
hisreach…HOW do you get rid of that annoying window?
Thanks,
Jim Vogel
:^)
Sorry, I didn't realize what I was leaving out of my message. You have to do
a 'Close' on the std-input or std-output variables that exist in the 'System'
module. I don't have the code in fron of me at this moment, but if you remind
me via e-mail, I will send you an example…Richie
Richie,
No I just looked in my manual, and can see how its done. Thanks for telling
me where it is at.
Jim Vogel
A thought just occured to me. The same "method" could be apllied to the
libraries. If you needed a particular version than just close and then open.
I presume the lib pointers are global. They are aren't they?
I assume you're trying to get rid of the window that's implicitly opened if
you're running from Workbench. The way to do this is to Close(StdInput) and
setting StdOutput to NIL. StdInput & StdOutput are in module System. The
unfortunate thing about this scheme is that the window is still opened for a
moment (until you close it) so it shows up as an unsightly flash. Oh well…
– Steve –
I haven't recieved the package yet. My concern is the problem
that Richie mentioned in his review of the startup code
opening all the Libraries for you, which might make it hard
to verify that the correct versions are available.
Thanks for the info on the Window.
Mike
Good point about the problem of not knowing whether the right version of the
libraries are opened.
– Steve –
This actually has a workaround solution. Close the libraries, and re-open
checking for version. Ugly, but it will do the job…
…Richie 🙂