There's a big difference between platform independence in theory, and actual platform independence. You can't just ignore the whole "compiling it" step when evaluating what's easiest.
I get the...
Type: Posts; User: brewbuck
There's a big difference between platform independence in theory, and actual platform independence. You can't just ignore the whole "compiling it" step when evaluating what's easiest.
I get the...
I think you're asking, why do we have this "return" concept when the function could just stick its result in a variable?
Well... it could do that. But the variable would have to be global,...
A frequently-changed header file that is included nearly everywhere is a design smell.
TBH, the entire stack of web technologies is a complete disaster, Javascript is just one part of it. Even if Javascript was amazing and perfect, CSS would still be horrific, HTML still terrible, and...
Well, you can
MyClass& self = *this;
self[123] = 345;
I don't really have much time to write responses anymore, unfortunately. I didn't mean to make a stinging criticism, just pointing out that I thought OP's question was being misinterpreted. If it...
I read that reply. It's not answering the OP's question.
It sounds to me like OP doesn't understand what it means for a function to "return." You guys are talking about the meaning of the possible...
The inquisitor clearly doesn't understand what "returning" means, so you fellows' explanations are not really very helpful. Maybe step back and actually pay attention to the question.
You haven't explained what your problem is with the presence of these UD2 instructions. Do you not test your code?
EDITED: thought it was Epy I was replying to.
Your test cases failed! Yay! The system works! What's your problem again?
Let's get this part correct. Your code with undefined behavior doesn't work.
I think the shame is that you've...
Your pet frustration notwithstanding, clang is pretty much taking over everything now. Android and iOS are both compiled with it, and Microsoft is switching to it. Get over it, man.
I'm just not moved to tears by the use of a function pointer...
My biggest problem with this code is the complete lack of tests. I mean, not a single test to be found anywhere. It also has "break"...
The source code of Clang.
I've looked over this code before. It's... eh... decent, I guess. There are plenty of tricks and hacks that make the code fast enough to pull off a really awesome video game -- and I don't dispute...
You shouldn't validate data in more than one place. There are several problems with doing it.
1. Dead code. If the code is validated at Point A and also at Point B, then it is possible Point B...
Abstraction always improves things.
For instance, you have a dynamic array that you add things to and you need to deal with resizing it.
Non-abstract route: everywhere in the code you need to...
C is unnecessary. It's too bad there are certain very high-profile people who refuse to let it go. Otherwise it'd be dead and buried by now.
How long is a piece of string?
You know what though? No. Programmers don't emphasize testing enough. I think as a general statement that's fairly safe.
EDIT: Oh... but as far as code coverage...
That's the thing though. It's up to you to decide whether you're getting paid a fair amount for your services. You're working more than the standard 40 hour week, but is it worth it? Maybe it is,...
I've done this both ways. Having two separate codebases is waaaaay easier.
Of course, if you have a bit of truly platform-independent code, go ahead and factor that out into a native library, but...
It requires help. You need support from more senior, more respected, more irreplaceable team members to stand up with you. Each of us has been treated like garbage at some point during the beginning...
If you cared about code size you'd be using .NET
Nobody should be using MFC or Win32 directly any more. It's arcane and doesn't expose the full feature set of Windows in a usable way. I wouldn't use C++ in any form for UI code on Windows, it's just...
rsync for Windows is a thing...
Writing native code for Android is not unheard of (it's a big part of what I do at work). But writing an entire app using nothing but native frameworks sounds impossibly painful. I'd stick with Java...