[Info-vax] Can C #includes like this be made to work onVMS?

[Arne Vajhøj]

On 10/16/2024 9:34 PM, Craig A. Berry wrote:
> On 10/16/24 5:44 PM, Arne Vajhøj wrote:
>> On 10/15/2024 7:48 PM, Arne Vajhøj wrote:
>>> $ type bc.eve
>>> all replace "#include ""b/" "#include ""c/"
>>> exit
>>
>>> $ type cd.tpu
>>> eve_all_replace("#include ""c/", "#include ""d/");
>>> eve_exit();
>>
>> Just realized that one is custom not standard.

>> procedure eve_all_replace(fndstr,rplstr)

> eve_all_replace may be custom, but as far as I know eve_global_replace 
> is standard.

Yes - it is.

I wonder why I have that eve_all_replace.

>       Here's an example of using TPU as a poor man's Perl:
> 
> $ edit/tpu/nodisplay/noinitialization -
>      /section=sys$library:eve$section.tpu$section -
>      /command=sys$input/output=myfile.txt myfile.txt
> input_file := GET_INFO (COMMAND_LINE, "file_name");
> main_buffer:= CREATE_BUFFER ("main", input_file);
> POSITION (BEGINNING_OF (main_buffer));
> eve_global_replace("foo","bar");
> out_file := GET_INFO (COMMAND_LINE, "output_file");
> WRITE_FILE (main_buffer, out_file);
> quit;
> ^Z
> 
> But yeah, Perl is way easier:
> 
> $ perl -pi -e "s/foo/bar/g;" myfile.txt

Of course.

:-)

Arne