As a style thing, I'd be quite happy to initialise everything inline once, but if I need to re-initialise then I'd want to be sure everything is the same second time around, so I'd probably use 'procedure expose' to initialise (and 'signal on novalue' as well, to avoid being caught out by different behaviour on the second time around).
There's nothing wrong with 'signal', of course, except that a lot of people reading the code won't be expecting it :-) Roops On Fri, 15 Mar 2024, 00:43 Phil Smith III, <[email protected]> wrote: > For me, this prompts discussion over "Is using SIGNAL worse than not > modularizing the initialization?": > > /**/ > stuff > signal DoInit > DoneInit: > . > > DoInit: > numeric digits 40 > . > signal DoneInit > > ----------- > > Discuss :) > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
