HP3000-L Archives

May 1995, Week 2

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:
Tony Furnivall <[log in to unmask]>
Reply To:
Tony Furnivall <[log in to unmask]>
Date:
Sat, 6 May 1995 10:24:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Ken Sletten b894 c331 x2525 <[log in to unmask]> writes:
 
>2)   If an MPE C++ compiler were enhanced after the
>initial port, what capabilities would it need:  indicate
>"don't care", "useful", or "must have" for each ?
>        Intrinsic support:
>        Access to IMAGE:
>        Access to KSAM:
>        Long pointer support:
>        Ability to run in MPE Name Space:
>        Use default MPE naming conventions:
>        Other >________________________:
 
 
Ken - good news on the C++ thing. My response comes from a different
perspective - but in answer to question 2 on your survey, unless a language
provides easy access to KSAM/IMAGE etc I don't think it's a viable language
on the HP3000. (See my diatribes elsewhere about the lingustic bill of rights).
I also think that direct support for MPE/iX code management tools is another
basic necessity.
(Steps down from soapbox and wipes sweat from furrowed brow)
Thanks.
Tony

ATOM RSS1 RSS2