Yeah, you just came off like sound like you knew better. It's alright.
It's perfectly understandable if you want to do it your way. Just don't say CornedBee didn't warn you ;)
Printable View
Yeah, you just came off like sound like you knew better. It's alright.
It's perfectly understandable if you want to do it your way. Just don't say CornedBee didn't warn you ;)
Hey, I'm fine with whatever you decide to do, and I don't have a problem with the wording of your post either. I think you're setting yourself up for failure (possibly depending on what you consider success), but that's an important part of learning, too. Time will tell.
I see what you mean now with using generic programming, together with boost::variant; I have thought about and I think it sounds like a good idea. However, the purpose of the library was not to have as few types as possible, but rather as many usable types as possible, even if I would start out with only one or a few. I know there will be a lot of coding, but that’s alright; it's expected. Maybe I'm doomed to fail, but then as you say, I will at least have learned something. ;)
I thought the purpose was to interpret user input as mathematical calculations.Quote:
the purpose of the library was not to have as few types as possible, but rather as many usable types as possible
Well, yeah, but various kinds of mathematical expressions. It depends on how much I want to put into it. I'm not making the library because I think that it will be used, but rather because I want to see what I can get out of it. I always experiment with programming like this to see what things that are possible to create. A new idea I have however, is to simulate two-dimensional fluids using a finite element method approach rather than using particles that most applications do today. But that is a completely other story. :)