Re: Using ref

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Peter wrote:

We're not. There are fundamental differences in the way the parameters
are used when you have a language that actually supports passing "by
reference", as compared to a language that does not.

That said, I'm done trying to help you understand. Every time you think
you've come up with an example that illustrates why things are the same,
we point out why the example is wrong. You either ignore those points
altogether (and why not? why bother to listen to any fact that conflicts
with your own view?), or you come up with some new example that is
similarly flawed (repeating the cycle).

You obviously aren't interested in learning something new. You reject
anything that confronts your own pre-established beliefs, and frankly, I
find religious debates pointless.

At least for the time being, this thread has sufficient content to avoid
any naïve reader thinking that you actually know what you're talking
about, and that's good enough for me. As I said, I don't really care what
_you_ believe...I just don't want anyone else thinking you're right. I'm
sure that goal has been accomplished.

Just to beat a dead horse and debunk your usual "Hilton's own view" opinion,
I did a quick search and found stuff on multiple university web sites and in
books teaching/showing "pass by reference" using C - here are some links,
but "pass by reference" using C is in many many many places:

http://www.youtube.com/watch?v=Dw76YHFQjaw (note the title)
http://www.cs.princeton.edu/~lworthin/126/precepts/pass_val_ref.html - "With
pointers, we can pass the values 'by reference.' Passing by reference means
that we'll pass the addresses of the variables instead of the values."

It's silly getting all heated up about these discussions. Again, your view
(which is consistent with Jon and many others) is that it is how it looks
and works from the source code point of view - fine, I have no problem with
that. But to me (and many others), that is mostly academic, what concerns
me is what is actually happening - i.e. is the entire array or just a
pointer/reference to the array being passed.

Having said that, I understand your frustration with another point of view.
I don't like hearing the media say that a plane stalled when its engine
stopped. Although we can blame the Wright brothers for this one. :)

Hilton


.

Relevant Pages

  • Re: 3rd and Final Post OCX Design Question
    ... whether there would be any difference in speed hit by creating the array on ... the client and passing a reference to the array or passing the picture and ... >> What is the difference between passing a picture as IPictureDisp as ... > the reference to the object. ...
    (microsoft.public.vb.general.discussion)
  • Re: segfault w/ block, but not file scope
    ... >>> Passing by reference has to do with passing around actual containers ... >> The language itself supports absolutely squat in regards to another ...
    (comp.lang.c)
  • Re: segfault w/ block, but not file scope
    ... >> Passing by reference has to do with passing around actual containers ... > The language itself supports absolutely squat in regards to another ... it is a mechanism of the language. ...
    (comp.lang.c)
  • Re: Passing arrays ByVal vs ByRef
    ... the value itself if you are passing a Value Type. ... the reference to the value if you are passing a Reference ... reference type (such as an Array), you get a copy of the reference (the ... not the object data that is being passed-by-value, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Can I get COBOL to look in a mirror?...
    ... > how do I reference each member of each structure? ... any 01 level with subsiduary items. ... > an array or structure is the table that I am passing as an argument ... You are not passing an 'array', you are passing a record. ...
    (comp.lang.cobol)