I posted in this forum to get help and the only thing i get is insults on how the code looks.Ok i agree that the code is not very clear because of it's appearance but your behaviour is not nice.ok you told me about the code but please do not make comments like you might not be a beginner but you are far away from understanding the software proper developing.
Oh yes, like maintenance and code re-use.Originally Posted by nicolassp
We'll just ignore those two "small" ones
>> ok you told me about the code but please do not make comments like you might not be a beginner but you are far away from understanding the software proper developing.
It wasn't meant as an insult; I was merely pointing out the obvious. The code you posted is completely convoluted, lacks modularity, and is quite unmaintainable. It's simply not acceptable, and doesn't qualify as "proper software development". I'm sorry if that offends you.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
You've painted yourself into a heck of a corner with that program's design, is what they mean.
It's good advice, because if you follow it, you'll not have this kind of trouble, again.
For now, here's what I'd do:
1) id parts of your code that is functionally different from the rest of the program, and
add a double line break above
and below it.
2) Add print statements to your major variables, in parts of the code where it's crashing.
3) Watch the rest of your variables in an IDE, as you step through your program
4) Either correct or rem out /* */ parts that are causing problems, even if it makes your program inaccurate right now, until you get code that will compile and run.
5) Now go back to the parts that are rem'd out, and de-bug them until you can get your program accurate, once again.
Nevermind the harshness of the critique of your program - they're just being honest. In a PC world, that's sometimes shocking, but it's also refreshing if you don't take it personally.
I have done the same stunt myself, and probably every programmer has, until they learn not to let their programming skills run ahead of their programming organizational skills.
Good luck!
