pointer which is pointing to new~

Hi guys~

when I read some tutorial files something confused me a bit this moment. the code is as follows:

int *pPointer;
void SomeFunction()
{
pPointer = new int;
*pPointer = 25;
}


what about the new here ?

And this line: pPointer = new int;
is pPointer pointing to the address of new int or to its value ? :rolleyes:

Regards~

new is a keyword which lets the compiler know that yolu are dynamically assigning memory while the program runs. Instead of the compiler allocating the memory from the get go, it waits until it reaches that line of code on the program execution and then assigns a memory address to it. It is normally used for making dynamic array and object factories(and things like that).

Quote:

---

And this line: pPointer = new int;
is pPointer pointing to the address of new int or to its value ?

---

Its pointing to its address.

YOUR CODE:

int *pPointer;
void SomeFunction()
{
pPointer = new int;
*pPointer = 25;
}


MY REVISION:


void function()
{
int *pointer;
pointer=new int;
pointer=25;
delete pointer;
}

void charpointer()
{
char *pointer;
pointer=new char[25];
pointer='\n';
delete [] pointer;
}

Golden Bunny, your revision is wrong. Your aren't dereferrencing the pointer before you assign a value to it. Also, after you delete a pointer created with new you need to set it to NULL.

why set it to NULL? it compiles fine........will it decrease the program's overall memory?(diskspace)

Quote:

---

Originally posted by Traveller
new is a keyword which lets the compiler know that yolu are dynamically assigning memory while the program runs. Instead of the compiler allocating the memory from the get go, it waits until it reaches that line of code on the program execution and then assigns a memory address to it. It is normally used for making dynamic array and object factories(and things like that).


Its pointing to its address.

---

address of new, let me see ...............

is it a dynamic one ?

I'm sorry, if you're trying to be sarcastic I'm totally missing something, otherwise I'm just not getting what you're getting at.

edit:

If I'm wrong with something please feel free to correct me.

Quote:

---

Originally posted by Golden Bunny
why set it to NULL? it compiles fine........will it decrease the program's overall memory?(diskspace)

---

You're kidding, right? Are do you have absolutely no clue? What do you think happens if you try to reuse a pointer that was deleted but not set to NULL?

Quote:

---

Originally posted by black



address of new, let me see ...............

is it a dynamic one ?

---

Yes. That's why it's called a dynamically allocated pointer.

If you're still confused ( as GB obviously is ) read this.

Quote:

---

Originally posted by jdinger


Yes. That's why it's called a dynamically allocated pointer.

If you're still confused ( as GB obviously is ) read this.

---

I'd really appreciate ur explaination, Jdinger~ ;)

I'll check the page u pointing to and back with questions several hours later, aha~ :D

Code:

---


#include <stdio.h>
#include <stdlib.h>
#include <conio.c>
int main()
{
 int n = 12;
 int *np;
 np = &n;

 int *created = new int;

 *created = 1000;

 printf("\"np\" points to: %i, which is of course: %i  \n\n", *np, n);

 printf("\"created\" points to: %i, so where is the variable it points to???\n\n", *created);


 created = np; //...Oh no, the integer "1000" is now lost forever...
 printf("Re-attaching \"created\" to something else...\n\n");


 printf("\"np\" points to: %i, which is of course: %i  \n\n", *np, n);

 printf("Now \"created\" also points to: %i, so where is the variable it pointed to before?\n  Can you see where it went?\n\n", *created);



getch();

return 0;
}

---

Quote:

---

why set it to NULL? it compiles fine........will it decrease the program's overall memory?(diskspace)

---

Well, what you are doing with the delete keyword is freeing the location that pointer is pointing to. Even though the pointer was "deleted" it still exists, only now it points to an invalid location. Most of the time this isn't a problem, but it can cause some big problems when it does happen, so it's a good habit to get into.

MacLeod

>will it decrease the program's overall memory?(diskspace)

Memory is not diskspace, it is RAM