next »

[Klaim]

If you fail for too long to see the problem, maybe invest some time in trying a static analysis tool, they are good at finding the source of such kind of errors.

[DantronLesotho]

A* pathfinding shouldn't be so difficult to conceptualize in the framework of a language. Sure it's easy to say "you check this and this and this" but to get it together in a reasonable manner (for the first time anyway) maddening.

[Geti]

Re: A* almost every explanation of it I've seen is shitty and I think that's a large part of the problem. My condolences.

[Kekskiller]

Only thing I needed to understand it was a well-made animated iteration with different colors different parts/positions of the algorithm. The associated text, however, always sucked and didn't really do much. I think Wikipedia did it rather well.

[Kekskiller]

I just met a C++ programmer who didn't know what fclose does. Yes, fclose. A muthafackin FCLOSE.
I hope he was on drugs or so. It can't be that bad, can it.

[Polly]

I just met a C++ programmer who didn't know what fclose does.

To be fair, fclose is ( a remnant of ) C .. not C++.

[Graham-]

I met a lisp programmer who didn't know what a list was. Then I realized he didn't know what anything else was, so didn't need a word for list.

what's c++

[Kekskiller]

I just met a C++ programmer who didn't know what fclose does.

To be fair, fclose is ( a remnant of ) C .. not C++.

That doesn't matter. It's as part of C++ as of C and I'd expect a C++ programmer to atleast know the standard library cause C++ doesn't cover everything. It's an expression of how barely some C++ programmer know what actually behind all their C++ stuff. That's why I'm grumpy.

[Graham-]

what makes a language a language?

can he express ideas competently in c++? I know guys who know apis out their ears, but then they use objects improperly. what defines improper? clearly less clear than what is otherwise available, less secure, less robust - however you want to describe it.

I don't know any language really. But if you gave me a task I'd just start coding it. I'd decide the language later, even if I already have a given compiler/interpreter .

[Polly]

That doesn't matter. It's as part of C++ as of C and I'd expect a C++ programmer to atleast know the standard library cause C++ doesn't cover everything.

To be fair, C++ does cover file I/O ( f/if/ofstream )

[Kekskiller]

Have you lost your minds? This is the grumpy programmer room, don't even attempt to turn my mood right now.

To be fair, C++ does cover file I/O ( f/if/ofstream )

And now think about how this is usually implemented. M$ compilers don't count.

[Graham-]

You could be using this as an excuse to get grumpier. Use your powers of grumpiness! ... Don't be a drone. Choose your path.

[Kekskiller]

I'm not sure if I should take this seriously or become more grumpy because you may want to make me less grumpy by forcing me to think about.

AHHHHHHHHHH

[Endurion]

Have you lost your minds? This is the grumpy programmer room, don't even attempt to turn my mood right now.

To be fair, C++ does cover file I/O ( f/if/ofstream )

And now think about how this is usually implemented. M$ compilers don't count.

So, who's this M-Dollar, and what does he do different?

[Kekskiller]

A magician of folk, spreading and stinky advertisements. Also created one the most non-legacy legacy compile systems ever made in the history of ultimate cross-platform grumpyness.

[Geti]

@kek oh man he's probably never seen a FILE* and thinks structs in C are the same as structs in C++ (and will happily try to add a constructor and then send emails when it doesn't work).

We have these guys at uni. I think it is actually that bad. These are the people that will be writing the software of tomorrow. Please send help.

... I secretly hope that they're just lacking experience and they'll develop into fully rounded programmers who read before they write and all that good stuff, but I've got a feeling they wont.

[Kekskiller]

No, you don't understand. He's not a rookie nor is not in knowledge of the difference between C and C++. He's even using C libs, funcs and structs in his code but he simply doesn't know what fclose is. You can't just hide this from yourself for like 2 years of professional C++ programming. It's as if it never existed and sudden this "new library function" pops up everywhere. And he's not even a dum guy or anything.

Every time someone mentions C functions it's most probably memory management, string functions or file operations. It simply can't be but it just is. I wouldn't even have a problem if he's rookie cause we all learn but someone who is getting paid for knowing stuff like that? The single leading C++ UI programmer if the whole team? Seriously?

Whatever. I'm getting over it. Eventually. In time. Or not. Who knows. Just-don't-think-about-it's-going-to-be-all-right.

[Graham-]

I programmed in Javascript for quite a while before I knew what a prototype was.

[Impmaster]

I don't think you need to know how to program in the slightest to know what a prototype is.

[BorisTheBrave]

Why on earth would a C++ developer use fclose when there is fstream or external libraries? I have been a C++ developer for over 4 years including time working with C and fortran, and have still never needed nor bothered to get to grips with the garbage C++ imported from C. It's not there because it's useful and cool, it's there for compatibility.

Knowing that std::fstream is implemented in terms of fopen is irrelevant - you might as well castigate Java programmers for not knowing about fopen, or a C user for not knowing about brk.