<*Chuckle*> I first heard that one as "You can write assembler in any language"!
Peter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, October 12, 2017 9:28 AM To: [email protected] Subject: Re: Rehabilitated TROT Routine (Was: Detection of Compile-Time Self-Modifying Code) On 2017-10-12, at 00:34, Rob van der Heij wrote: >> >> DO WHILE,TROT,R14,R2,B'0001',1 >> ENDDO >> > Constructs where evaluation of the condition has a side effect (or > completely relies on the side effect) are often more a convenience to the > writer than to the reader. > When working in a language that encourages it, I try to restrain myself to > common constructs like testing a null pointer with the assignment. There's > something to say for languages where it's left to the compiler to optimize > that. > Perhaps. OTOH, in POSIX shell, I loathe such novice constructs as: some-command if test $? = 0 then other-command fi ... instead of the simpler, intuitive to me: some-command && other-command I've known novices to go to outrageous constructs to avoid using compound symbols as associative arrays. It pays to be familiar with the power of your language. "You can write FORTRAN in any language." -- gil 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.
