Re: arrays = pointers?
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Thu, 01 Mar 2007 15:07:27 +0800
On Thu, 01 Mar 2007 03:57:17 +0800, Göran Andersson <guffa@xxxxxxxxx> wrote:
The documentation actually uses the term "pointer", but that is used for pointers. :)
Sorry...I didn't think it was necessary to explicitly state that I was simply talking about what the .NET documentation uses to describe references. Of course it uses the word "pointer" elsewhere, just as it uses all sorts of other words that also do not describe .NET references.
Yes, it's much simpler than any of those two. The inner workings of a reference is just a pointer, nothing more. What makes a reference different from a pointer is simply how the compiler allows you to use it.
It is obviously not "just a pointer". Either the compiler, or the .NET Framework, or both, hide the inner workers from the programmer. But for the reference to be relocatable, *some* kind of extra work has to be done. Whether that is for the reference to be a pointer to a pointer, or if there is some table of relocatable pointers somewhere, or something else, I don't know. But clearly for .NET to be able to relocate the object that a reference refers to, there must be more than just a simple pointer to that object.
Pete
.
- Follow-Ups:
- Re: arrays = pointers?
- From: Göran Andersson
- Re: arrays = pointers?
- Prev by Date: Re: CSharp
- Next by Date: Re: Does C# have static local variables like C++?
- Previous by thread: Re: arrays = pointers?
- Next by thread: Re: arrays = pointers?
- Index(es):
Relevant Pages
|
Loading