Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!mcvax!kth!enea!sommar
From: sommar@enea.se (Erland Sommarskog)
Newsgroups: comp.editors
Subject: On TPU types
Message-ID: <4418@enea.se>
Date: 7 Apr 89 22:41:25 GMT
Organization: ENEA DATA AB, Sweden
Lines: 21

Gregg Wonderly (gregg@ihlpb.ATT.COM) writes:
>TPU variables inherit type information from assignment.  The types supported
>are
>
>    INTEGER, KEYWORD, STRING, PATTERN, MARKER, RANGE, BUFFER, WINDOW,
>    PROGRAM and ARRAY.

Which is both true and untrue. There are actually two more types, 
namely key maps and key-map lists. It's just that you refer to 
them through strings. They were thrown in afterwards with V1.2
of TPU (shipped with VMS 4.4) in a quite ugly way. 

They are quite useful though. A key-map list is something you
associate with a prefix key. (At least that is what I did.)
Then I have different key-maps since there are some functions
I want to have disabled being the message buffer while others
I only want in the message buffer.
-- 
Erland Sommarskog - ENEA Data, Stockholm - sommar@enea.se
I used to say "It could have been worse, it could have been Pepsi",
then I drank a Diet Coke...