Re: pointer as argument and parameter
On Nov 29, 2:56 pm, Eric Sosman <Eric.Sos...@xxxxxxx> wrote:
Inside foo itself, the types of the function parameters
are whatever you said they were. Again, you tell the compiler
something, and it's the compiler's job to remember.
I hope this helps.
Yes indeed it helps a lot. (Please excuse the double version of the
question...I thought I had successfully removed the first).
What you say makes a lot of things much clearer, and places the role
of the compiler in a new light for me.Thank you.
.
Relevant Pages
- Re: a case for multiple inheritance
... and overrides the write functions to change ... the compiler would optimize it so that the double function call would be ... private new void Foo ... The cast not much ...
(microsoft.public.dotnet.languages.csharp) - Re: a case for multiple inheritance
... the compiler would optimize it so that the double function call would be ... private new void Foo ... The cast not much ... This means that if method A1 overrides ...
(microsoft.public.dotnet.languages.csharp) - Re: a case for multiple inheritance
... and overrides the write functions to change ... the compiler would optimize it so that the double function call would be ... private new void Foo ... The cast not much ...
(microsoft.public.dotnet.languages.csharp) - Re: Operation can be dispatching in only one type
... to say that uninitialized is what the programmer wants. ... Some fancy means to tell the compiler that this variable ... So Java speculates that the default constructor is somewhat ... Yes, this is legal, because Foo is called with X having been ...
(comp.lang.ada) - Re: Sacla loop: a new loop implementation
... >> Finally, once the foo macro receives its argument, then based on what ... >> depending on how the macro is defined. ... transformations and optimizations deep in the bowels of the compiler, ... > available at macroexpansion time. ...
(comp.lang.lisp) |
|
