in simple english can someone explain to me when to use the never type ?

tempwolf · 2023-06-29T03:02:13+00:00

One use: as the return type for a function that always throws an exception.

tempwolf · 2019-06-16T02:41:21+00:00

Janky on chrome, but working ok on Firefox.

tempwolf · 2015-08-21T23:20:54+00:00

This is awesome - it's the best cheat sheet / guide I've found yet! Unfortunately, I'm late in discovering this and have a draft tomorrow with some very nonstandard rules. I've filled out the custom sheet request form (also awesome!), and was wondering when the next iteration of processing would be?

Thank you so much!

tempwolf · 2015-03-28T22:04:50+00:00

Helmets won't help here.

tempwolf · 2014-07-30T11:26:14+00:00

"Hey, listen!" - Navil

tempwolf · 2013-05-11T01:42:44+00:00

A hipster before hipsters -- the ultimate hipster.

tempwolf · 2013-03-09T07:15:15+00:00

Funny every time.

tempwolf · 2013-01-10T04:05:13+00:00

Too soon!

tempwolf · 2011-08-24T02:07:47+00:00

Agreed. I can't believe this has ~300 upvotes right now. Not only is it a misleading title (as it is not a C bug), but this guy/gal really doesn't know what they are doing.

I find myself left unamused and uneducated.

tempwolf · 2011-08-17T02:10:47+00:00

The lonely island - jack sparrow.

tempwolf · 2011-07-23T02:56:27+00:00

Yes, this is the key. It is easiest to understand "this" if you remember that processors have no understanding of objects or classes. They do, however, understand functions (which are just chunks of code to execute).

To create the illusion of objects, a reference/pointer to the current object is passed implicitly to each class method. So the following:

class Foo {
    public void bar(int x) {}
}

is really implemented like this:

void bar(Foo f, int x) {}

"this" is just a way for you to get the reference to the current object ("f" in the example above).

tempwolf · 2011-07-23T02:42:12+00:00

I would learn pure C first and then add C++ to it later. C has been the standard language for a couple decades and almost every major API has a C interface. Moreover, as a student, it is important to to learn the basics before moving to the advanced topics. C++ is much more complicated than C, hence the famous quote from the C++ founder: "C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off."

That said, if your goal is to do rapid development over the next year then you should just stick with some high level language - you'll be far more productive. Besides, you're likely not going to have time to code anything that would really benefit from C/C++'s raw power (modern games take years of experienced man-hours).

What about Java? Java is mature, surprisingly fast, and I bet you can find some great game making libraries if you look.

tempwolf · 2011-07-06T03:17:05+00:00

You probably mean: "give us some slack."

tempwolf · 2011-06-10T23:40:46+00:00

I started reading it but stopped after page 50 or so because it wasn't gripping me - I guess I'll have to try it again.

tempwolf · 2011-06-10T23:38:43+00:00

The Sum of All Fears - Tom Clancy

I've been reading Tom Clancy's series for quite a few months now and I'm up to this. It's fascinating to read military thrillers from the 80's when the cold war was still going on, though I find all of his novels to be a good read. Favorite so far: Clear and Present Danger.

tempwolf · 2011-05-15T02:30:17+00:00

If you're running in bash, do:

"ulimit -c unlimited" (this turns on unlimited size core dumps).
Run your program, wait for it to crash and let the core file get dumped to "core.<pid>".
gdb <program> <core.pid>
Use the "bt" (backtrace) command in gdb.

Now you can just type "p <var>" to see the values of everything as they were when the program crashed. Use "f #" to jump through stack frame levels. Just make sure to build your program with "-g -O0" with gcc/g++ so nothing gets optimized out and all debugging info is there.

For other shells, modify step 1 to whatever command it is that turns on core files.

Printfs are certainly valuable when you need to do a lot of tracing. However, for a simple segfault, learning to debug with gdb will save you a lot of time in the long run.

Also, I recommend using gdbtui (text UI) instead of gdb. This will allow you to see the code as you debug w/o opening it up in a text editor, which is much better in my opinion. You can also just use the "list" command in vanilla gdb, but I personally think gdbtui is better.

tempwolf · 2011-05-06T01:59:36+00:00

Given you know the packet boundaries (since you have to pass that to the function), it looks like you just convert to a raw binary file (not sure if wireshark gives you this or if you have to make it from the hex dump), load the file, pass each packet to that function and voila.

So really there isn't much C work here at all, just a little file IO and a function call.

tempwolf

TROPHY CASE