Hi,
I am working on an OOP project, and cannot decide which way to follow when
I have to write a simple function.
For example, I want to write a function which generates a random string. In
an OOP environtment, it is a matter of course to create a static class and
a static method for that. But
2013/9/19 Simon Dániel simondan...@gmail.com
Hi,
I am working on an OOP project, and cannot decide which way to follow when
I have to write a simple function.
For example, I want to write a function which generates a random string. In
an OOP environtment, it is a matter of course to create
I think that it would be more elegant if you are already in a OOP to keep
the flow and stick to OOP. It just doesn't make sense to me in an
environment that uses OOP to have functions laying around.
Personally I like to group similar functionality together in their own
objects, this way I can
On Thu, Sep 19, 2013 at 06:28:32PM +0200, Simon Dániel wrote:
Hi,
I am working on an OOP project, and cannot decide which way to follow when
I have to write a simple function.
For example, I want to write a function which generates a random string. In
an OOP environtment, it is a matter
2013/9/19 Aziz Saleh azizsa...@gmail.com
I think that it would be more elegant if you are already in a OOP to keep
the flow and stick to OOP. It just doesn't make sense to me in an
environment that uses OOP to have functions laying around.
buzzword: multi-paradigm. Thats why it could make
5 matches
Mail list logo