FOR loops

Article View: comp.lang.modula2

Article #870

#870

From: Bri
Date: Tue, 03 Jul 1990 20:54

14 lines
1072 bytes

In regards to my FOR loop question, Peter states that such a construct
might introduce many difficulties into the loop control code.

I can not find any such difficulties. In fact, most other high-level langauges
will support such a sequence of statements. The RECORD example that he showed
is still not understandable to me. To repose the question I ask instead of
a record how about a POINTER TO INTEGER?
Again, the same rule applies that such a variable can not be used as an index.
To me, there is no difference between p@ and i where p is a POINTER TO INTEGER
and i is an INTEGER.

Anyone else have any answers as to why Wirth designed such a restriction?

Bri

Technical Details

Message-ID: <INFO-M2%90070316593556@UCF1VM.BITNET>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!UCF1VM.BITNET!ROSS

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!UCF1VM.BITNET!ROSS
From: ROSS@UCF1VM.BITNET (Bri)
Newsgroups: comp.lang.modula2
Subject: FOR loops
Message-ID: <INFO-M2%90070316593556@UCF1VM.BITNET>
Date: 3 Jul 90 20:54:15 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Modula2 List <INFO-M2%UCF1VM.BITNET@PSUVM.PSU.EDU>
Organization: The Internet
Lines: 14