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:
Scott Herman <[log in to unmask]>
Reply To:
Scott Herman <[log in to unmask]>
Date:
Wed, 10 May 1995 09:58:43 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
At 09:47 AM 5/10/95 METDST, Chris Breemer wrote:
>> 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:                      must have
>         Access to IMAGE:                        must have    <<==****????
>         Access to KSAM:                         must have    <<==****????
>         Long pointer support:                   must have
>         Ability to run in MPE Name Space:       must have
>         Use default MPE naming conventions:     must have
>
>It is imho not an option to release an initial port without these features,
>and then go and enhance it. Better wait awhile longer for the real stuff.
>
 
I am curious and would appreciate some explanation of how IMAGE and KSAM
might be supported in a standard compliant c++ compiler, and how this sort
of support might differ from intrinsic support. TIA
 
 
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:                                                                           :
: Scott Herman          [log in to unmask]   Yale-New Haven Hospital
:
: Dept of Lab Medicine                                       20 York Street :
: (203) 785-2449                                       New Haven, Ct. 06504 :
:                                                                           :
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

ATOM RSS1 RSS2