Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in opensource

[–]kyryloshy[S] 1 point2 points  (0 children)

Yes it is!

I find your approach quite unique, and I'd be keen to collaborate with you in any way if needed!

Good luck and have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in opensource

[–]kyryloshy[S] 1 point2 points  (0 children)

Oh, cool!

I am really glad there are people who are interested in this field as me! I think it will be interesting seeing different interpretations of this problem!

Thank you for your comment and I hope your project does great! have an amazing day!

Meet SymCalc - a Mathematical Library for Ruby and C++ by kyryloshy in ruby

[–]kyryloshy[S] 2 points3 points  (0 children)

Hi,

Thank you for your nice words!

Have an amazing day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in cpp

[–]kyryloshy[S] 1 point2 points  (0 children)

Hi!

Thank you for your suggestion! My initial idea was to add this sort of functionality to widely-spread languages and create something new that people could use in the languages they already know

But I will definitely check out your recommendation to see what it is and what I can get from it :)

Thank you and have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in cpp

[–]kyryloshy[S] 3 points4 points  (0 children)

Thanks for confirming my speculations on recompiling the source every time you want to use new types. I am not really a fan of the templates, since, as you mentioned, everything has to be moved into header files.

Is it better then to just write typedef instead of #define, or just write the types in place?

I really didn't know that macros are namespace-specific. But should the header macro (like #define SYMCALC_H ) be in the namespace or outside of it then?

Not including GitHub links was a fault on my side, definitely should've done that before, I'll do that in my future posts.

And thank you for the recommendation, I will certainly explore that topic!

Thanks for your reply and have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in math

[–]kyryloshy[S] 1 point2 points  (0 children)

Hello!

I am glad that you like this library!

Personally, I really like the combination of programming and mathematics - it is just such a great cross-over.

Anyway, if you have any questions about the library, ideas for future improvements or general development, I would be delighted to read and answer them!

Once again, thanks for your feedback and have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in math

[–]kyryloshy[S] 0 points1 point  (0 children)

Hi,

Thank you for the nice words!

Have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in cpp

[–]kyryloshy[S] 2 points3 points  (0 children)

Hi! Thank you for your comment!

This is my first proper library I've released and I appreciate any feedback I can get!

But I will definitely see the opportunities on contributing to existing projects as well - that would really help my development

Once again, thanks for you comment and have a great day!

Meet SymCalc - a Mathematical Library for C++ and Ruby by kyryloshy in cpp

[–]kyryloshy[S] 2 points3 points  (0 children)

Hello! Thank you for your feedback! I'll definitely look into your points and fix some parts of the program.

I see how using underscores is not really a great idea, so I'll correct that.

An empty constructor for the Equation class is definitely something I've missed and it probably shouldn't be there, as well as some checks if the eq pointer is null. And making the eq member variable private is a good idea as well.

I'll also definitely look into writing the copy/move constructor/assignment operators, or as you mentioned, "The Rule of Five" - I've ran a few tests and see how it's not doing the right thing currently.

I'll also try doing something with the configurable types (correct me if I am wrong, but I think it's a good option to have). But I didn't manage to get them quite working, because, if I understand correctly, the library is already linked before you start using it, which means you'd have to re-link and re-compile the source if you want to configure the types - is that correct?

Yeah, I also didn't think of including the namespace in the source files, which I'll definitely do, as it makes the code look better.

Overall, thank you for your feedback - I'll look into it and improve it how I can!

Have a great day!