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:
Shankar Unni <[log in to unmask]>
Reply To:
Date:
Sat, 13 May 1995 01:30:50 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
Scott Herman ([log in to unmask]) wrote:
 
> >         Access to IMAGE:                        must have    <<==****????
> >         Access to KSAM:                         must have    <<==****????
 
> 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
 
The Intrinsic mechanism is flexible enough for most purposes: the compiler
can simply treat the intrinsics as automatically extern "C", with the
appropriate calling interface gleaned from the $SYSINTR files..
 
The Data Dictionary is something else, though..  I don't think the C
compiler supported it, either..
--
Shankar Unni                            E-Mail: [log in to unmask]
Silicon Graphics Inc.                   Phone:  +1-415-390-2072
URL:    http://reality.sgi.com/employees/shankar

ATOM RSS1 RSS2