Re: How to enter tiny Binary Floating-Point value
If you give themthe tool, the will find a use. For completeness, and for those who really push th limits, how hard is to create that data type?ZA Sent from Yahoo Mail on Android On Wed, Aug 2, 2023 at 11:52 AM, Jonathan Scott wrote: Shmuel (Seymour J.) Metz writes: > That still leave the question of HLASM syntax for DC. I would > hope that it's been extended to handle tiny floating point. This has not been done so far, as the architects said it should not be needed, as it was not for general programming purposes. When the architects added the BFP tiny format (that is, the IEEE 754 half-precision binary floating-point format: binary16) we asked whether this format should defined in Assembler, and we were told not to bother, as it was primarily for use as a data format for NNTP input which would normally be generated by a compiler or obtained from other sources. If someone submits a requirement showing a strong justification for making the format available in Assembler, I think that our existing IEEE floating point conversion routine should already be able to handle it, so the main things to be resolved would be what to call the DC type and what type attribute it should have (given that all upper case letters and some other characters have already been used). Jonathan Scott, HLASM IBM Hursley, UK
Re: How to enter tiny Binary Floating-Point value
Ref: Your note of Wed, 2 Aug 2023 16:55:30 + > I believe Jonathan was referring to âNNP-Data-Type-1 Formatâ, not > the old âNetwork News Transfer Protocolâ. Too many acronyms . . . ð > > Peter Should have been NNPA. I'm currently off sick and thought I had recovered enough to answer that pending question, but perhaps my brain still needs more rest! Jonathan Scott, HLASM IBM Hursley, UK
Re: How to enter tiny Binary Floating-Point value
I believe Jonathan was referring to “NNP-Data-Type-1 Format”, not the old “Network News Transfer Protocol”. Too many acronyms . . . Peter From: IBM Mainframe Assembler List On Behalf Of Paul Gilmartin Sent: Wednesday, August 2, 2023 12:14 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: How to enter tiny Binary Floating-Point value On 8/2/23 09:52:47, Jonathan Scott wrote: > Shmuel (Seymour J.) Metz writes: >> That still leave the question of HLASM syntax for DC. I would >> hope that it's been extended to handle tiny floating point. > > This has not been done so far, as the architects said it should > not be needed, as it was not for general programming purposes. Are there hardware instructions supporting the format? Could it be generated with a library macro? > ... it was primarily for use as a data > format for NNTP input ... Ah, Usenet. I remember it fondly. Does LISTSERV rely on NNTP? > > ... the main things to be resolved would be > what to call the DC type and what type attribute it should have > (given that all upper case letters and some other characters > have already been used). HLASM appears to have made a bad design choice in making the case attribute case-insensitive. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: How to enter tiny Binary Floating-Point value
On 8/2/23 09:52:47, Jonathan Scott wrote: Shmuel (Seymour J.) Metz writes: That still leave the question of HLASM syntax for DC. I would hope that it's been extended to handle tiny floating point. This has not been done so far, as the architects said it should not be needed, as it was not for general programming purposes. Are there hardware instructions supporting the format? Could it be generated with a library macro? ... it was primarily for use as a data format for NNTP input ... Ah, Usenet. I remember it fondly. Does LISTSERV rely on NNTP? ... the main things to be resolved would be what to call the DC type and what type attribute it should have (given that all upper case letters and some other characters have already been used). HLASM appears to have made a bad design choice in making the case attribute case-insensitive. -- gil
Re: How to enter tiny Binary Floating-Point value
Shmuel (Seymour J.) Metz writes: > That still leave the question of HLASM syntax for DC. I would > hope that it's been extended to handle tiny floating point. This has not been done so far, as the architects said it should not be needed, as it was not for general programming purposes. When the architects added the BFP tiny format (that is, the IEEE 754 half-precision binary floating-point format: binary16) we asked whether this format should defined in Assembler, and we were told not to bother, as it was primarily for use as a data format for NNTP input which would normally be generated by a compiler or obtained from other sources. If someone submits a requirement showing a strong justification for making the format available in Assembler, I think that our existing IEEE floating point conversion routine should already be able to handle it, so the main things to be resolved would be what to call the DC type and what type attribute it should have (given that all upper case letters and some other characters have already been used). Jonathan Scott, HLASM IBM Hursley, UK
Re: Macros: sublists question
Just because a positional sublist parameter works for one (or two) thing doesn't mean you're limited to using only positional sublist parameters. Maybe add a keyword TYPE=EQ, or whatever makes sense? Much more typically, the blinders are on the other side, and people forget that a positional parameter would be much better than a required keyword of FUNCTION=foo|baz sas On Wed, Aug 2, 2023 at 2:55 AM Rene BRANDT < 14a2846c6667-dmarc-requ...@listserv.uga.edu> wrote: > Hi David, > > I don't understand your need of the = sign, and a question comes to me : > why not using a 3rd parameter ? > > René > >
Re: Macros: sublists question
Maybe. Have you tried a solution using AINSERT? Or would that get too messy? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf of Rene BRANDT [14a2846c6667-dmarc-requ...@listserv.uga.edu] Sent: Wednesday, August 2, 2023 2:54 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Macros: sublists question Hi David, I don't understand your need of the = sign, and a question comes to me : why not using a 3rd parameter ? René Le mardi 1 août 2023 à 23:12:07 UTC+2, David Eisenberg a écrit : Thank you very much, everyone, for these rapid and helpful replies! I hear you all loud and clear... my concept is apparently wishful thinking. I will put the equals sign inside the parentheses so that the parameter is treated as a sublist. David
Re: Macros: sublists question
Hi David, I don't understand your need of the = sign, and a question comes to me : why not using a 3rd parameter ? René Le mardi 1 août 2023 à 23:12:07 UTC+2, David Eisenberg a écrit : Thank you very much, everyone, for these rapid and helpful replies! I hear you all loud and clear... my concept is apparently wishful thinking. I will put the equals sign inside the parentheses so that the parameter is treated as a sublist. David
