decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
GOTO and COMEFROM | 361 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
GOTO and COMEFROM
Authored by: argee on Sunday, May 20 2012 @ 03:48 PM EDT
There is also CONTINUE which is a place
marker you can GOTO or GOSUB to, or RETURN to.

It allows for easier editing/bypassing/debugging.

We are speaking of MS BASIC here, with line numbers.
Not all BASICS had line numbers.

Ah! The days of the Altair 8800. I have three of them
still, and one IMSAI 8080. Basic, Assembler, dBase II,
VEDIT, etc. CP/M 2.2, Altair DOS, Altair BASIC. Heady
days, those!

---
--
argee

[ Reply to This | Parent | # ]

GOTO and COMEFROM
Authored by: Wol on Sunday, May 20 2012 @ 04:47 PM EDT
The other thing I've used (which was actually very useful) was the longjmp()
function in PL/I (the Pr1me version - I think called plp).

Really meant for error handling. I can't remember the name of the setup function
but it stuffed a "come to" marker on the stack. Then if you hit an
error, you could longjmp() to the marker and it would unwind the stack, exiting
all the intervening subroutines you'd called. If you forgot (or messed up) to
set up the "come to", the stack would unwind all the way and the
program would crash.

But as I say, a VERY useful trick for handling errors. I've not really
programmed with OO languages and exceptions, but I think the PL/I way of doing
it was much better - it permeated Primos in the versions I was used to, and I
found it very easy to use.

Cheers,
Wol

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )