In this context, missing means no reference to the element since the latest initialization and dropped means there was a drop after the last initialization with no subsequent reference.
foo.=bar /* foo.bar, foo.baz, foo.foo are all missing */ drop foo.bar /* foo.bar is dropped, foo.baz and foo.foo are missing */ -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Tuesday, July 2, 2024 4:37 PM To: [email protected] Subject: Re: Rexx is quite cool, flexible, powerful, feature-rich, thank you! (Re: z/OS 3.1 Enhancements & Support News On Tue, 2 Jul 2024 20:05:13 +0000, Seymour J Metz wrote: > ... >> What is the signifiaance o f the "name" of a stem? > >It's the value returned by the STRING method. It's also the default value for >missing (not dropped) elements. > Is the distinction between "missing" and "dropped" elements an incompatibility with TSO/E REXX, for which: <https://www.ibm.com/docs/en/zos/3.1.0?topic=instructions-drop> DROP "“unassigns”" variables, that is, restores them to their original uninitialized state. IOW, do SYMBOL(), VALUE(), etc. return the same result for missing, uninitialized, and dropped elements? -- gil ---------------------------------------------------------------------- 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
