rwessel (rwessel.delete@this.yahoo.com) on March 21, 2021 11:34 am wrote:
> rwessel (rwessel.delete@this.yahoo.com) on March 21, 2021 11:26 am wrote:
>
> > Wasn't the come-from instruction/statement defined by a (humorous) Datamation article
> > back in the 70s, as a response to the structured "goto-less programming" proponents.
>
> Datamation, December 1973:
>
> https://web.archive.org/web/20180716171336/http://www.fortran.com/fortran/come_from.html

Since I graduated in '73 perhaps this is a case of early onset cryptomnesia (the scourge of inventors)

Mine used a come-from stack that compared the top of stack to the pc and returned to the top of the loop (stored on the stack along with the come-from address). It would have been great for handling COBOL perform statements since you could in theory perform code from any paragraph(?, think block). So an arbitrary paragraph might drop thru or return to a point after an invoking perform. Performs were sort of parameter-less subroutine calls, where the subroutine was any arbitrary group of paragraphs. If I screwed up the description, it was a result of time and trying to forget COBOL.