HP3000-L Archives

August 1999, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 31 Aug 1999 11:45:07 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
Re:

> Same for me. I admit I am sort of flabbergasted by these commands ;-), even
> after my own 18 years on MPE boxes.

me too!  (20 years)

> > PS. Does anyone remember using ALLOCATE to hold commonly used programs in
> memory
> > on classic machines? This is about as obscure as I get. I bet a lot of
> people
> > out there still do this. <g> I also remember writing my first VIEW

I still ALLOCATE some CM programs today, on MPE/iX 6.0 ... for the same
reason as on Classic MPE: to speed up create/createprocess.

Christian posted a nice summary of the benefits/internals of ALLOCATE.

> Ah, the good ole' times of :ALLOCATE and :AUTOALLOCATE !!! Ah, these CPU-

I regret the loss of AUTOALLOCATE :(

> AFAIK, ALLOCATE does not do anything on MPE/iX.

AFAIK, it does exactly the same thing on MPE/iX as it did on MPE V.

It does save some elapsed time:

Example...running P.PUB (begin/end.) 100 times:

   not ALLOCATED:  3,282 CPU, 9,705 elapsed milliseconds

   ALLOCATED:      3,342 CPU, 7,733 elapsed milliseconds

--
Stan Sieler                                          [log in to unmask]
                                         http://www.allegro.com/sieler/

ATOM RSS1 RSS2