[Info-vax] Native compilers

[VAXman- at SendSpamHere.ORG]

In article <sv5ias$ute$1 at news.misty.com>, Johnny Billquist <bqt at softjar.se> writes:
>On 2022-02-22 16:06, VAXman- at SendSpamHere.ORG wrote:
>> In article <sv2i58$a5h$1 at news.misty.com>, Johnny Billquist <bqt at softjar.se> writes:
>>> {...snip..}
>>> Uh? What? Either I am confused, or you are.
>>> ..INCLUDE /whatever/
>>> should work just fine. It's not that Macro-32 don't have an include file
>>> system. It's just that it's not the only thing it has. It *also* have
>>> libraries, which is something Unix compilers usually lack when we talk
>>> about source side.
>> 
>> There is no .INCLUDE directive in Macro-32!  It is not referenced in the
>> VAX Macro LRM either.  Adding a ".INCLUDE /whatever/" elicits the error:
>> 
>> 	.INCLUDE	/whatever/
>> ^
>> %AMAC-E-UNRECSTMT, unrecognized statement
>> at line number 173 in file SYS$SYSROOT:[SYSMGR]X.MAR;3
>> 
>> 
>>> Or at least this is what I *know* is true in Macro-11, and while it's
>>> been quite a while since I played with Macro-32, I'm fairly certain it's
>>> the same there.
>> 
>> 'Tis not!
>
>Ok. This time I'm really surprised. Makes one wonder why this was 
>removed in Macro-32, which certainly otherwise feels like a spiritual 
>successor to Macro-11.
>
>And I certainly believed I had used it in the dim past when I played 
>more on VAXen. Brains develop bit rot...

Personally, I prefer the macro library mechanism.  If you need to ".INCLUDE"
put it in a macro library, reference the library (.LIBRARY) and then callout
the module.  The idea is reusable macros.  One time Macro-32 should simply be
put into the source.
 

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.