RogueP2

Yeah, this is myg0t where all the twelve year olds, who don't know shit about computers, come to pretend and talk trash. The rest of us just come here to feel superior over them, and laugh when they stay something stupid, which is quite often. Just remember, when they know nothing about a subject, they resort to pointing out your grammar mistakes, or dispute their own sexuallity by projecting it onto others.

Yes I do know that, and my last line should have been a "shouldn't" not "should" (I think that should be pretty obvious). As for visual basic.net and vista, I doubt it'll be too much of a change. The change will mainly be to the .NET Framework. VB6 to VB.NET was a huge change, because they had to make it OOP in order to comform to .NET specs. Check the 3.0 specs if you want to see what will be added to VB.NET.

Accessing the API isn't that difficult in a .NET, not sure how it is with VB.NET seeing as it doesn't have pointers (I know it can be done though), but in C# its just a matter of telling the compiler where to look and which function you want. From there, you can just write a wrapper class for it to simplify its use (basically what you should be doing in C++ anyways). Also Managed C++ has direct access to native C\C++ code and .NET, so if you really wanted, you could go that route. Most of the time you'll be using the .NET framework though. Here's a C# article on how to do the above for Keystroke mining: Basic Keystroke Mining Once you know VB.NET, it shouldn't be too hard to get what you want from it. EDIT: FIXED

C is good for apis, embedded systems (portability), and code needs to reach the most programmers as possible. If none of the above apply, go with a higher language. Just choose the right tool for the job, and move in that direction. There are always going to be things you can do in C/C++ languages, that you can't do in Java or .NET (C#, VB.NET, etc). This goes the other way to, there's things you can do in Java/.NET that you can't do in C/C++. I personally suggest going down the ladder, than going up it. You'll enjoy writing code in Java or C# more than C++, especially at first. You'll also spend less time worrying about which library to use. In any case, if you want to see what C# can do, check out RunUO. Its a Ultima Online server emulator, so you can play the game on a free shard, instead of paying. It was developed relatively quickly compared to other UO emulators, and became stable very quickly. Taking into account that this server must keep track of a lot of objects across a vast multilayer world at all times; its pretty amazing achievement.

All languages have their purposes. Java can do almost everything C/C++ can do, and vice versa. Of course there is always lowlevel things that Java will have a hard time doing, but this goes the other way too, there are things that lowerlevel languages would have a hard time doing as well. So don't let people discourage you.

I think you're refering to VPNs (Virtual private networks).

This can easily be done using ssh, and works fine with NAT Overloading. As for VLANs, I have no idea what your talking about. VLANs are used on switches, to split the broadcasting domain, so broadcasts do not overwhelm a lan with a huge amount of devices. Routers, by default, already split the broadcast domain.

Why are you still iterating over the alphabet? All the loop is doing is determining whether nlist is between 'A' and 'Z'. Unless you're going to treat some of the letters differently you're just adding overhead. Also use the letters instead of the code, its much more readable. Better yet, use the isalpha() or isalnum() functions, it is much more portable. In either case, their basically just doing a simple if condition like: // isalpha/isalnum checks for lower case letters too ('a'-'z') if (nlist[i] >= 'A' && nlist[i] <= 'Z' || nlist[i] >= '0' && nlist[i] <= '9') With a few exceptions, this does the same thing as your's does: // headers, nlist definition int main(int argc, char *argv[]) { int i; for(;;) { for(i = 0; nlist[i] != 0; i++) { if(::GetAsyncKeyState(nlist[i]) == -32767) break; } if(nlist[i] == 0) { continue; } else { if ( isalnum( nlist[i] )) // if letter or number { char letter = tolower(nlist[i]); // converts to a lowercase char std::cout << letter << std::endl; // output to screen } else { std::cout << nlist[i] << std::endl; // otherwise, output code to screen } } } }

Yeah, they didn't have to offer opengl at all for AeroGlass.

The choice is a matter of opinion. If you need portablity, use opengl, if you plan on sticking to windows, use directx. The performance lost only affects applications that run on the desktop, not applications that run in full screen mode (i.e. games). The reason for the performance lost is because Aero Glass only uses DirectX, and thus OpenGL must be wrapped over the underlining DirectX API.

First off, you're assigning x to i in the last if statement, this will always evaluate to true, and so you're just outputing the 'a' through 'z'. You should be using a '==' instead of an '=', so it reads "if (i == x)". The other thing wrong with this if statement is that you're comparing i, which is the array index, to x, and not comparing nlist (the captured key) to x. Same goes when you pass to the Translate() function. Next problem is that if the if statement fails, your just outputting the value currently in nlist to the screen, which doesn't increment until the containing for loop ends. Here's what happens when you type A and press enter. for( x = 65; x <= 90; x++ ) { if( nlist[i] == x ) // loop 1: 65 == 65 (true); loop 2: 65 == 66(false) { Letter = Translate(nlist[i]); // loop 1: pass 65 to Translate; returns 'a' std::cout << Letter << std::endl; // outputs 'a' } else // loop 2 { // loop 2: outputs 65, 'i' doesn't get incremented, continutes to output 65 until loop exits std::cout << nlist[i] << std::endl; } } As you can see, you'll need to move the else to outside the for loop. In reality, the best thing to do if you still want to use your Translate function is to do something like: // Replace the above for loop with this: if (nlist[i] >= 'A' || nlist[i] <= 'Z') // <cctype> has a isalpha() function that is more portable { Letter = Translate(nlist[i]); std::cout << Letter << std::endl; } else { std::cout << nlist[i] << std::endl; } Now what I would do is is just replace the above with a simple cast instead of bothering with translating specific characters: std::cout << static_cast<char>(nlist[i]) << std::endl; Hopefully this all makes sense.

Um. . .duh, of course it is a superset, but the reality is that C++ isn't a complete replacement of C. But what is really funny, is that if everything I say is so obvious, then why is the most you can say is C is better because the other language sucks.

Its true that a well written C application can also be compiled as a C++ application, but there are some differences. C++ is much more type-safe than C, also there are some differences in the methodologies between a C and C++ programmer. For example, a C programmers uses macros, and pointers much more than a C++ programmer would/should (inlines, templates, references, etc). Also, C is favored in situations where you need to control how the final code is compiled, such as in the case of linux kernel where you need to be able to predict functions names (i.e. different implementations name overloaded functions differently). Also, C is much more compatible between languages than C++; almost every language has some way to call a C function. So your choice between C++, and C, depends heavily on what you're trying to solve. In most cases you should choose C++ over C though, since it allows you to write applications in a much more abastract way, and allows you to overcome many of the lower-level problems like memory management.

LOL, actually, your more like a sheep giving into hype, and if you're saying C is perfect for every job, then you've proven me right. Otherwise, as I said before, give me examples where C is more superior for the average application. I've done a lot of work with C in both Linux, and Windows environment (as well as other languages like C++, C#, Java, Perl, LISP, Ruby, and python) over the course of the past 10 years, and I always evaluate a language based on the problem at hand. Someday, you may actually grow up, and realize that just because a language is popular, doesn't mean its the best language for a particular job.

You're pussy, because you obviously don't program in either language; atleast, not anything serious. C is great for when you need to write low-level, language portable, APIs, or on specialized hardware; the rest of the time you're adding bugs, security risks, and reinventing what other languages already provide. I mean atleast use C++. So why don't you go back to sucking your mom's dick.. Otherwise, show some intelligent and give more reasons than "This language sucks, like your mom does", or "This language rules because it fucked you in the ass last week".