@Sven > There is not necessarily a right and a wrong way. Design is hard to > explain, I am not going to try. Sorry ;-)
Of course! I was just trying to find out the design *norm* for a small problem; to become familiar with the popular way of thought among Smalltalk'ers. @kilon Thanks. I think that may be what I need: real world examples. As I have already admitted, I am not used to Smalltalk way of thinking. This is the first language I know, that enforces OOP by design, none of Java, Python, C++ or Scala does. It's ironic; OOP concepts and techniques were among the first things I was taught back in University but now the more I think about Smalltalk's syntax and design, the more I get closer to the conclusion that I didn't use pure OOP many times during my career. And, I believe, it was simply because the development platforms never enforced it the way Smalltalk does: in a clever and camouflaged way. > But please do have a look at the Chronos library, it even has a PersianCalender, among many others. I knew about Chronos. Someone here, kindly suggested it about 6 months ago when I asked about such a thing. I'm not trying to re-write something like Chronos rather I'm trying to get my hands dirty with Pharo and also re-visit my OOP skills. Thanks. -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com)
signature.asc
Description: OpenPGP digital signature
