[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
:: before global functions
- To: <eric@son-of-blob>
- Subject: :: before global functions
- From: Ravi Pandya <ravi@xxxxxxxxxxx>
- Date: Mon, 9 Apr 90 14:08:59 PDT
- Cc: <tribble@son-of-blob>, <xtech@son-of-blob>
- In-reply-to: <eric@son-of-blob'smessageofMon>,04 PDT <9004091658.AA08922@xxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 9 Apr 90 09:58:04 PDT
From tribble Sun Apr 8 18:09:39 1990
From: tribble (Eric Dean Tribble)
Subject: :: before global functions
I just made all global functions print with '::' before them. I had a
case where the method 'black' was calling a global functions named
'black'. It got very confused....
Note that we already put '::' before pseudo-constructors. My only
worry is that this will put :: before inappropriate things. 'Integer
IntegerVar: num' will translate to '::IntegerVar(num)'.
::IntegerVar(num) doesn't work at all. Hugh and I have fixed my version
of the translator to print :: in front of all functions, except IntegerVar:,
which seems to be a unique case (if others are found a more general solution
will be needed).
This change is in ech-b.cha. Also in this file there are various compilability
fixes as well as a repair to the CxxBrowser so that it believes that the text
is saved when you ^S on a meta class definition text pane.
- e - with the assistance of heh
There are a couple of places where the Manipulator code calls global
functions that translate to macros in C++. They will not work with ::
in front of them. We can either (a) use some criterion like upper case
letters or (b) have a list of functions shouldn't have ::
(sounds better to me); anything without a :: shouldn't have spaces
after the comma either, as it screws up symbol concatenation. (I put
in a hack for this that we should take out once we get a better