A good book on pointers,memory and some inner workings of compilers for C++

[Hypernova]

I am searching for a book(s) which explains things like the following -

1. Difference between memory allocation of local and global (or other static variables)....? (or why i cant initialize a global variable more than once outside main and all other functions)

2. Holes in structures, and structures and pointers.

3. Deep concepts in pointers, objects, classes.....i mean relation between pointers and OOP.

4. near, far, Huge pointers.

5. Some insight into how the compiler does something....I dont want to know the exact details of compiler working, but there are some concepts I feel can be better understood if i know how compiler does it.

I have already tried Pointers In C by Yashwant Kanetkar and didnt find it very useful.
I am finding that the C++ Programming Language by Bjarne Stroussoup answers some of these questions, but i want a bit more detail, and a dedicated book for this.

I found that a book named "C++ Pointers and Dynamic memory management by Michael C. Daconta " which seems to hold these answers, but i cant find the book anywhere in my city to get it and see if its really worth it (and there's no preview on internet). So please tell me if its a good book for this purpose, so i can order it online.

[helios]

or why i cant initialize a global variable more than once outside main and all other functions

Because the global scope is not there to write code. It's there only to declare and initialize stuff. A variable/object can only be initialized when it's declared, so...

2. Holes in structures, and structures and pointers.

What do you mean?

3. Deep concepts in pointers, objects, classes.....i mean relation between pointers and OOP.

OOP doesn't deal with pointers, so there's no relation. C++ just happens to have both pointers and OO.

4. near, far, Huge pointers.

There's no such thing. At least not in C/++. It's not inconceivable that some Assembly has something like that, though.

5. Some insight into how the compiler does something.

Do you have anything in particular in mind? "Something" is rather broad.

[jsmith]

4. is a remnant of the DOS/Borland compiler days.

5. no, at least not for a C/C++ compiler. You can find books that teach the theory behind compiler construction and probably provide source for a very small language, though.