home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!bu.edu!wang!news
- From: s2861785@techst02.technion.ac.il (Alon Ziv)
- Newsgroups: comp.lang.pascal
- Subject: Re: Turbo and Procs/Fns as params..
- Message-ID: <S2861785.92Nov19085756@techst02.technion.ac.il>
- Date: 19 Nov 92 08:57:56 GMT
- References: <1992Nov4.190755.25383@polaris.utu.fi> <mByRTB4w165w@digsol.jpunix.com> <1992Nov11.104939.14727@jyu.fi> <1992Nov11.111534.1@uwovax.uwo.ca> <1e6qnoINNnr6@matt.ksu.ksu.edu> <dmurdoch.163.721919129@mast.queensu.ca> <SHEN.92Nov16212135@nil.IRO.UMontreal.CA>
- Sender: news@wang.com
- Organization: /u1/023/s2861785/.organization
- Lines: 33
-
- In article <SHEN.92Nov16212135@nil.IRO.UMontreal.CA> shen@nil.IRO.UMontreal.CA (Yu Shen) writes:
-
- [...stuff deleted]
-
- I just have a related problem that it seemed to me that member
- function can not be as value for such procedure variable.
-
- [.sig deleted]
-
- This is just one example of the serious defect in TP Func/Proc
- parameters: that is, all that is passed is a pointer to the code, and
- not the scope. This limits the use of Func/Proc parameters to global
- procedures and functions, and disallows passing the address of a
- nested function, for instance.
-
- [ As an aside, in some TurboVision units you DO have to pass such a
- function; however, this is done [ugh!] by passing pointers around and
- using dirty ASSEMBLY tricks to get it working... And it's
- incompatible even with StonyBrook Pascal+, which is the nearest
- thing to 'TP-compatible'... ]
-
- -az
- ---
- Internet: s2861785@tx.technion.ac.il . __
- I'M A STUDENT: When I'm wrong, it's my teacher's fault _| /
- (when I'm right, the credit is all mine!) / | /_
- Alon Ziv
-
- --
- Internet: s2861785@tx.technion.ac.il . __
- I'M A STUDENT: When I'm wrong, it's my teacher's fault _| /
- (when I'm right, the credit is all mine!) / | /_
- Alon Ziv
-