[Info-vax] C99 updates to CRTL
John Reagan
xyzzy1959 at gmail.com
Tue Jul 30 20:10:17 EDT 2019
On Tuesday, July 30, 2019 at 5:13:12 PM UTC-4, Stephen Hoffman wrote:
> On 2019-07-30 16:45:43 +0000, hb said:
>
> > On 7/30/19 3:58 PM, Stephen Hoffman wrote:
> >> On 2019-07-29 17:50:54 +0000, John Reagan said:
> >>
> >>> On Monday, July 29, 2019 at 12:21:28 PM UTC-4, Stephen Hoffman wrote:
> >>>> There's already at least one logical name around that effects the
> >>>> compile-time behavior.
> >>>>
> >>>> One existing logical name effects the compile-time resolution of the
> >>>> external references within the compiler.
> >>>
> >>> Do you have a reference?
> >>
> >> The DEC/Compaq/HP/HPE/VSI C compiler opens up the C RTL and searches it
> >> for a list of entry points, and that processing can be redirected by
> >> logical name. I don't recall off-hand if it was the DECC$SHR logical
> >> name, or if some other was used.
> >
> > Sounds like DECC$CRTLMAP, which by default points to SYS$SHARE:DECC$SHR.
>
> Yeah; that's the logical name. Thanks.
>
> This logical name dreck either never gets documented, or doesn't get
> documented very well, and the parsing code is inevitably bespoke, and
> the calls and doc scattered hither and thither.
>
> Less design than app API architectural accretion.
>
>
>
> --
> Pure Personal Opinion | HoffmanLabs LLC
To be honest, that logical is only designed to be used as part of the CRTL build itself where I want the compiler to prefix newly written routines that are not part of the build system's installed CRTL. It would never be used in the real world.
More information about the Info-vax
mailing list