OOP - Class Design

[jeisma]

Hi!

I'm in very early stages of OOP. Coming from a procedural programming, I'm starting to see the change in mindset when designing my application.

My first project:

Convert numbers, date, time values in different languages. Language is not known until run time.

This is how I designed my classes.

Interface ILang. With methods num_to_words(), date_to_words(), time_to_words().

And above interface implemented by these classes: French. English. Spanish. German...

I'm not comfortable about this design. Maybe I should have a class Number, or Date, or Time?

How would you design your classes? Which pattern works best with this scenario?


Thank you!

 

[douglasb]

Presumably, the "number", "date", "time", etc. would use the classes that are built in to most languages (Integer, for example). Or they would just be primitive types. At any rate, you are over-complicating it. You have a generic ILanguage and however many classes that implement it. For what you are trying to do, you really don't need to abstract it any further than that.

 

[douglasb]

What programming language?

 

[beginner99]

Dates, times, timezone etc are extremely problematic and not easy at all. Save your time it has been done and I very strongly suggest using a standard library for that problem regardless of language.

 

[clamum]

For your project, I'd say what you have is decent. No need to over-think it like douglasb metioned.

How about trying a simple game, like maybe Blackjack? Or check beginner C# of Java books/tutorials for ideas on simple apps to get the hang of OOP.

 

[eyahaloms]

I think its a good design. And I've been using C++ object oriented for 12 years.
Basically the client gets a ILang pointer (in Run time), which is basically a derived class
and does the conversion.