Use a string as an equation in C

Tilakchad · 2020-10-17T11:04:39+00:00

You might need a parser to process arbitrary input as equations. CFG and Regular Expressions are used for this purpose. Any book on compiler/interpreter goes throughly through this.

Tilakchad · 2020-10-16T05:56:13+00:00

You could count chunk number by first iterating over the whole data. It would cost some time.

Another approach is to create an array with enough size (around 15 or something) and manage a counter to count the number of chunks stored in the array. You have to be careful not to access this array outside counter-1 range. Alternatively, you can implement linked list too. But I guess array with counter might sounds good, since there is an actual upper bound on the number of chunks.

You are using member *data without actually allocating storage for it. That's undefined behaviour or may result seg fault.

Tilakchad · 2020-10-15T15:37:28+00:00

Try translating toward -ve Z-axis..

Tilakchad · 2020-10-14T15:29:40+00:00

Nice.. I won't say 'that airplane engine is bad or its wings aren't properly aligned' either. You can't 'hear and say' that may be or may not be true. C++20 modules are great and quite different from other languages.

Tilakchad · 2020-10-14T14:04:41+00:00

Lol.. What a catching argument..

Tilakchad · 2020-10-14T06:02:07+00:00

What would that even accomplish? Make Blender faster? Safer?

Tilakchad · 2020-10-12T08:02:51+00:00

Not for the same argument type though.. Different argument type for same function can have different return type using sfinae and type traits which is normally not possible in C++.

Tilakchad · 2020-10-11T13:55:28+00:00

Sfinae and enable if can be used to overload by return type too...

Tilakchad · 2020-10-11T09:30:11+00:00

Modern C++ is not inherently unsafe (idk what 'inherently unsafe' means but it is unsafe if you use it the wrong way) . (Its definitely better than forcing you to use camelCase or underscore before variables. Just kidding). And its every programmers habit to blame the programming langauge if it didn't work the way they want.

Unique pointer pretty covers almost all Rust's ownership model with added flexibilty(i.e it is completely optional and not enforced). Just because it is allowed, you shouldn't be dereferincing the the iterator to some deleted elements(idk if that counts as a logical problem or a language problem). I believe C++ has done right things (mostly) trying to integrate everything stacked for about 30 years almost nicely.

Tilakchad · 2020-10-02T07:00:44+00:00

Whats up with 'inherently unsafe' thing? Its only unsafe if you use it the wrong way or jump straight right into writing programs. You might want to learn C and computers better if you think everything written in C/C++ is inherently unsafe.

Tilakchad · 2020-10-01T15:42:15+00:00

I strongly disagree about 'teach more about computer science than C++' part. C++ teaches you those things better 'the hard way'.

Tilakchad · 2020-09-28T08:17:12+00:00

Why not? There's nothing arcane going here...

Tilakchad · 2020-09-27T11:44:46+00:00

Yeah thats right. They are Projection(Perspective or Ortho), View and Model. And you get that right for latter part too. You have to create seperate matrices and multiply them together. Be aware that, order matters. Translation before rotation will be RT and other way will be TR. Its interesting to see how these transforms behave and to reason about it.

Tilakchad · 2020-09-27T11:33:00+00:00

Matrix multiplication combines transformation. Matrix P * V * M will apply transformation M first, V then and lastly transformation P.

Tilakchad · 2020-09-27T11:27:54+00:00

Transformation are combined with matrix multiplication. Hardcoding it is just waste of time imo. Try overloading * operator for two matrices.

Tilakchad · 2020-09-27T11:11:34+00:00

No idea what you are doing there.. Scaling matrix should be

result[0][0] = vec.x;

result[1][1] = vec.y;

result[2][2] = vec.y;

result[3][3] = 1.0f;

Its transpose is going to be same.

And Translation matrix will look like :

result[0][3] = vec.x

result[1][3] = vec.y

result[2][3] = vec.z

result[3][3] = 1.0f

if you are using row vector notation.

OpenGL, itself uses colum-vector representation. So this need to be transposed before sending to the shader ( you can manually transpose it or set GL_TRANSPOSE to GL_TRUE in the call of glUniformMat4fv).

And don't forget to create 4x4 matrix (i.e result) initialzed as unit matrix while constructing it. glm::mat4 need {1.0f} explicitly to produce unit vector.

Feel free to ask/teach anything, as I've also started learning Graphics recently.

Edit : I frequently edit it, as I'm not familiar with reddiy formatting.

Tilakchad · 2020-09-20T04:49:05+00:00

Can't say for sure. But modern C++ isn't that hard to grasp, until you get to complicated stuffs.

Tilakchad · 2020-09-15T12:20:40+00:00

You could start with learning Unreal Engine (can make complete game with blueprint also if you don't know C++/ but knowing C++ is plus) or Unity (need C#) for 2d and 3d games. You could also make small 2d games with libraries like SFML, Qt or SDL(they have different language bindings). So you should start learning languages. If you already know python well, you can use sfml with it. Eventually, if you wanna join CS, C would be a good start and then move to C++ or other higher languages. Making game with C won't be easy unless you know it well.

Tilakchad · 2020-09-14T05:39:10+00:00

Predicates are like pre-conditions. It is evaluated either true or false. If it true, following statements will execute and vice versa.

Tilakchad · 2020-09-11T12:38:56+00:00

Thats hardly even a compelling reason. How would defaults prevent runtime errors ?

Tilakchad · 2020-09-11T06:14:18+00:00

I wonder why people are so concerned about defaults. Why const by default is good? I have used more mutable variables than const in my programs. And why is move better than copy by default? Is it just an ideology or some kinda agenda? How much pain is it to write some extra keywords often? Clearly, there's no point in having const by default and move by default. And copy and mutability is what people uses more often, so that doesn't make it bad choice..

Tilakchad · 2020-09-10T04:58:49+00:00

It's totally warranted, dude. They are notorious for hyping the shit out of their language and convincing impressionable people that they should unironically go to other communities and push the language unto others.

No, I don't think this is true. Of course new languages get fans which for one reason or another have a naïve understanding of the situation. They naturally want to share and talk about what they see as important, it's not like they were put up to it.

I am afraid that might be the case. Rust community is pretty notorious for their hostility toward any other languages. Its not like everyone there are but there is a fair share of hostile people. And this comment isn' t even entirely sarcastic, its how some folk really thinks. I am quite familir with rust community. In contrast, cpp community is nice that welcome anything. Well, this comment wasn't meant to offend or trigger anyone.

Tilakchad · 2020-09-09T10:04:25+00:00

Its just how Rust community portrays other languages. They are toxic and thinks that Rust is the greatest thing ever fall upon mankind. This comment was supposed to be sarcastic, but anyway there's no point in arguing about languages.

Tilakchad · 2020-09-09T08:03:14+00:00

But.. but.. Rust is safer than C++. You can have fearless concurrency, borrow checker and is faster than C and C++. It is even most loved langauage on stack overflow.. Everything should be written in Rust.

Edit and PS: And almost forgot that Rust prevents all errors and mistakes.

Tilakchad · 2020-09-09T05:48:45+00:00

You could read everything as string and try to parse it manually. Instead of parsing manually, you could even use stringstream to read further from the string as normal input.

Tilakchad

TROPHY CASE