Use of sppp.awk part 3

[chris hermansen]

Good afternoon everyone,

This is not a feature request but more of an idea for later...

For maintainability, I think that liberally sprinkling a module definition
with

{iter L {short short} {short} {} {long} {long long}}
{iter K {SHORTEN SHORTEN} {SHORTEN} {} {LENG} {LENG}}
{iter xlx {short_short_} {short_} {} {long_} {long_long_}}

... template with fields to be substituted indicated by {L}, {K}, {xlx}...

{reti {,} {;}}

(using my proposed extension here)

bulks up the code in an unnecessary and potentially error prone fashion.

What about having something like

{ iterates defined for int and bits modes }
{iteratesof IBL {short short} {short} {} {long} {long long}}
{iteratesof IBK {SHORTEN SHORTEN} {SHORTEN} {} {LENG} {LENG}}
{iteratesof IBxlx {short_short_} {short_} {} {long_} {long_long_}}

{ iterates defined for real and complex modes }
{iteratesof RCL {} {long} {long long}}
{iteratesof RCK {} {LENG} {LENG}}
{iteratesof RCxlx {} {long_} {long_long_}}

And then where we need the templating

{iter IBL}

... template with fields to be substituted indicated by {IBL}, {IBK},
{IBxlx}...

{reti {,} {;}}

and so on?

Or perhaps the {iter} could look lilke

{iter {IBL IBK IBxlx} {L K xlx}}

so that we don't have to edit the original {L}, {K} and {xlx} in the
templated code.

-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://gcc.gnu.org/pipermail/algol68/attachments/20260213/b97a8018/attachment.htm>