home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!UB.com!pacbell.com!ames!agate!spool.mu.edu!howland.reston.ans.net!paladin.american.edu!news.univie.ac.at!hp4at!mcsun!fuug!funic!sauna.cs.hut.fi!news.cs.hut.fi!mheiskan
- From: mheiskan@hut.fi (Mika Heiskanen)
- Newsgroups: comp.sys.hp48
- Subject: Re: What is a META ???
- Date: 28 Jan 93 18:09:35 GMT
- Organization: Helsinki University of Technology, Finland
- Lines: 45
- Distribution: inet
- Message-ID: <MHEISKAN.93Jan28200935@lk-hp-5.hut.fi>
- References: <1k7jn7INNmev@aurora.engr.LaTech.edu>
- Reply-To: mheiskan@vipunen.hut.fi
- NNTP-Posting-Host: lk-hp-5.hut.fi
- In-reply-to: ramos@engr.LaTech.edu's message of 28 Jan 1993 03:25:27 GMT
-
-
- In article <1k7jn7INNmev@aurora.engr.LaTech.edu> ramos@engr.LaTech.edu (Alex Ramos) writes:
-
- >The file entries.all (a new version recently on seq.uncwil.edu) lists
- >several entry points to handle "meta objects".
- >However, RPLMAN.DOC doesn't even mention them. I don't have a clue what
- >they are.
-
- Oops, I seem to have assumed the explanation was somewhere.
-
- A meta object is what you get when you explode a composite object.
-
- Example: { %1 %2 } <INNERCOMP> --> %1 %2 TWO
- '1+2' <INNERCOMP> --> %1 %2 + THREE
-
- The stack scheme ( Meta1 Ob Meta2 ) could thus mean for example
-
- 5: %1 \
- 4: %2 Meta1
- 3: TWO /
- 2: %0 - Ob
- 1: ZERO - Meta2 (Empty)
-
- The stack scheme for top&
-
- ( Meta1 Meta2 --> Meta1&Meta2 )
-
- means that the meta objects have been combined just be adding their 'length
- fields' e.g the binary numbers together.
-
- And for addt+
-
- ( Meta --> Meta&+ )
-
- means that '+' has been added to the meta object by pushing '+' to stack level
- 2 and by incrementing the count.
-
- ( Thus :: top& addt+ ; would be a very simple adding routine )
-
- In general handling meta objects is faster since building & exploding
- composites is time expensive. All low level symbolics handling is done via
- meta objects.
-
- --
- --> mheiskan@vipunen.hut.fi
-