Search results for query: *

i had noticed my model wasn't listed, so i didn't change it at first, wary of any screen corruption. but now that you mentioned it i went ahead and chose an older model of my monitor. it worked out fine. finally some breathing space on my desktop. it would still help to know how i could check...

finally i have installed a new system. Fedora 7 i386. guess i took your advice after all, thx. now it finds my ATI Radeon 9600 at install, but the maximum resolution i can set is 800x600 under Gnome. I figured this must be a driver issue so i wanted to make sure i had at least XFree86 4.3...

I have installed it on a 2001 pc, so it's not a new system. And i'm not planning on hooking it up on a LAN or anything, just the internet. i have no sensative data on that computer. i thought upgrading it to the latest drivers would be a good learning experience with regard to handling the bash...

^ 4.6.0 version of Xfree86 ofcourse, linux version is 7.3.

I should have mentioned it earlier, but i have actually installed version 4.6.0 now. i had this version of linux laying around for a couple of years and i thought that would be a nice starting point. i thought it doesn't matter what version of linux i take, if i want to upgrade it, i can...

hi, I installed redhat 7.3 and i wanted to install the drivers for my ATI Radeon 9600 video card. Their website stated that the drivers would only work with XFree86 4.3, i was running 4.2.0. So i downloaded Linux-ix86-glibc22 from the xfree86.org ftp site (i have glibc version 2.2). I verified...

Have you ever looked in the executable file to see if the comments are inside the code somehow? Your for loop above. If the main program is really inside it, it should have been written using the comma operator. There's nothing compact about that because the compiler generates more machine code...

it does work, i forgot that prototypes don't necessarily need argument names. i compiled it like this: int strlen(const char[]); main() { return 0; } int strlen(const char s[]) { return 0; } The prototype is legal, the function head would be illegal without the "s" argument name. The...

I found a piece of code in "The C programming language second edition ANSI C" which does not compile. Someone on this forum is bound to have it so i thought i'd post this question. It's on page 40 at the bottom. For the one's who don't have it: As expected, my compiler complains: error C2055...

seems to me that the double word stored at the address stored in eax is copied into the ecx register.

I understand now that reference variables can also be referred to as aliases, thanks. There's just one thing: They may be used the same, but internally (at the machine code level) they are very different. The symbolic constant is substituted with the actual integer address at compile time...

If an alias isn't a reference variable, then how do i declare an alias?

I've explored somewhat myself, everything points to the fact that aliases are the same thing as references. To bad though, this is not very consistent. I haven't got his books, but i wonder what Bjarne Stroustrup calls them.

yeah, the information i found always pointed to the fact that aliases are the same as references. I prefer the name alias though.

hi, i have just started out with c++. unfortunately the material that i'm reading does not explain the difference between what it calls alias variables & variable references. hope somebody knows. thx.

hi, i have just started out with c++. unfortunately the material that i'm reading does not explain the difference between what it calls alias variables & variable references. hope somebody knows. thx.

http://webster.cs.ucr.edu/AsmTools/WhichAsm.html

i have seen compiler generated assembly code a lot of times and it always strikes me how needlesly often it accesses memory. Whereas human written assembly code the processor registers are used whenever possible, a compiler accesses a variable 99% of the time from its address in memory. This...

i mentioned that after p0=p0->Next, p0 is a pointer to a pointer, but now i think i was wrong. all it did was copy the value of one pointer to another.

i've tried to cast the receiving pointer: (DATA*)p0 = p1; i had hopes it would accept it, but alas. i found a way around the problem. i have restructered my code so it won't have to do this assigment statement anymore, it's a bit longer now, but it works. thanks for the help.