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 12:34:33 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
At 07:58 AM 5/10/95 pst, Mark Klein wrote:
>Scott writes:
>
>>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
>
>Actually, what if IMAGE and KSAM were supported through a canned class
>library provided with the compiler? This could be implemented in such a
>fashion that the compiler wouldn't necessarily need direct intrinsic
>support.
>
>
How would you port such a class library to a Unix box?
And how would the class library access IMAGE and KSAM?
There are lots of other reasons why direct intrinsic support is neccesary.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:                                                                           :
: 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