Re: Enhanced Macro Library

Given the age of the compiler code (he did say MFT), they might be from the JESx predecessor product, HASP. HTH Peter -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Keven Sent: Friday, February 16, 2018 7:56 PM To:

Re: Enhanced Macro Library

It looks like macros from JES2 On Fri, Feb 16, 2018 at 3:50 PM -0600, "Dave Wade" wrote: Folks, Perhaps apposite to the recent

Re: Labels

From: "Jon Perryman" Sent: Friday, February 16, 2018 4:44 PM Seymour is talking about maintainable large amounts of code should have at least alphanumeric labels. Numeric labels can be confusing unless you have a really good numbering scheme. It still doesn't matter

Re: Enhanced Macro Library

Looks like JES2 to me Keven Hall JES2? On Fri, Feb 16, 2018 at 3:50 PM -0600, "Dave Wade" wrote: Folks, Perhaps

Re: Labels

From: "Paul Gilmartin" <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> Sent: Saturday, February 17, 2018 6:18 AM On 2018-02-16, at 11:33:05, Bernd Oppolzer wrote: IMO, Niklaus Wirth ... came to this decision, to allow numbers as labels only, and to force them to be declared before using

Re: Labels

On 2018-02-16, at 20:03:57, Robin Vowels wrote: > From: "Jon Perryman" > Sent: Friday, February 16, 2018 4:44 PM > >> Seymour is talking about maintainable large amounts of code >> should have at least alphanumeric labels. Numeric labels can be confusing >> unless you have a really good

Re: Labels

On 2018-02-16, at 18:45:04, Robin Vowels wrote: > From: "Paul Gilmartin" > Sent: Saturday, February 17, 2018 6:18 AM > >> On 2018-02-16, at 11:33:05, Bernd Oppolzer wrote: > >>> IMO, Niklaus Wirth ... came to this decision, >>> to allow numbers as labels only, and to force them to be declared

Re: Labels (was: Call by name)

On 2018-02-16, at 11:33:05, Bernd Oppolzer wrote: > IMO, Niklaus Wirth ... came to this decision, > to allow numbers as labels only, and to force them to be declared before using > them. > The prior declaration is (almost) necessary for single-pass compilation. We added identifiers as labels,

Re: Labels

Yes, sure, I forgot about that. Single-pass compilation makes the compiler fast; my Pascal compiler compiles itself (19.000 lines) in ca. 10 seconds. (And this runs interpreted on Windows, using a P-Code interpreter ...) On Hercules (CMS or MVS), it's about the same. There you have to add 3 or

Labels (was: Call by name)

IMO, Niklaus Wirth, when designing Pascal, decided to discourage the use of goto as much as possible. OTOH, he was not courageous enough to leave goto and labels out of the language. So he came to this decision, to allow numbers as labels only, and to force them to be declared before using

Re: Solution OOP in HLASM

Hello Jon, I do not, let me try once more I did not say, that you can't develop in HLASM in a OOP style, but the difference is, that you enforce these rules in OOP Languages. You mix C and C++ randomly. If you btw read my footer right you would realize I am not at all a C programmer. The only

Re: Labels (was: Call by name)

Using numbers for labels is certainly a good way to discourage goto's. Eliminating GOTO sure makes code a lot more readable and maintainable. Assembler toolkit has a set of structured programming macro's that greatly reduces the need for branch labels. I hated macro's that required branch

Re: Labels

Borland Turbo Pascal was blindingly fast for its time. Charles -Original Message- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Bernd Oppolzer Sent: Friday, February 16, 2018 12:05 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Labels

Enhanced Macro Library

Folks, Perhaps apposite to the recent conversation. I enjoy fiddling with old code. I was playing with a very old copy of VM which has a very old copy of the MFT FORTRAN G compiler installed. The heading in the listing file refers to an old University system. I have the "assembler" source to