Sujet : Re: Can C #includes like this be made to work on VMS?
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.os.vmsDate : 17. Oct 2024, 00:00:14
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vepghu$2e4fp$10@dont-email.me>
References : 1 2 3 4 5 6
User-Agent : Pan/0.160 (Toresk; )
On Wed, 16 Oct 2024 18:44:44 -0400, Arne Vajhøj wrote:
procedure eve_all_replace(fndstr,rplstr)
local fnd_string,
rpl_string, pos_mark, count_integer;
if not (eve$prompt_string(fndstr,fnd_string,"Old string: ",
"No old string given")) then
return;
When DEC introduced TPU/EVE, I raised my arms to the heavens in joy at
finally being liberated from the suffering that was EDT. (Hate EDT. Hate,
hate, hate.)
Then I left it behind with VMS ... and a few decades later, finally found
the time to get to grips with Emacs.
In Emacs/ELisp, there is the distinction between a “function” (what TPU
would call a “procedure”, I guess) and a “command”. A “function” only
becomes a “command” when you insert the “(interactive ...)” directive near
its start. This is a declarative construct that supplies the information
Emacs uses to obtain the right arguments for the function automatically,
including prompting the user as necessary, so your code doesn’t have to.