Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!dslg0849
From: dslg0849@uxa.cso.uiuc.edu (Daniel S. Lewart)
Newsgroups: comp.lang.pascal
Subject: Re: Why does this work in TP ?
Message-ID: <1990Dec20.023514.6325@ux1.cso.uiuc.edu>
Date: 20 Dec 90 02:35:14 GMT
References: <25295@adm.brl.mil> <1990Dec18.200336.13056@ux1.cso.uiuc.edu>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 17

dslg0849@uxa.cso.uiuc.edu (Some Idiot) writes:

> The second line of output is actually 'In MethodA'.  Chapter 5 of the TP 5.5
> OOP Guide, section 'Method calling conventions', states the following:
>      Methods always use the FAR CALL model, regardless of the
>      setting of the $F compiler directive.  [Capitalization is Borland's]
> Thus there is no unusual feature in the program; it is a legal OOP ability;
> it is not a violation of scoping rules; it can be explained; and it is a legal
> documented feature.

I'm sorry.  What I meant to say was:

The program does have an unusual feature; it is not a legal OOP ability;
it violates scoping rules; it can be explained as a TP5.5 bug; and it appears
to be a bug/undocumented feature.

Dan