splitting common functions into a sepperate module

[Marc 'BlackJack' Rintsch]

In <1173348733.037351.229990 at 64g2000cwx.googlegroups.com>, jonkersbart
wrote:

>> - wrapping the functions as methods of a class, passing the whole state
>> as args to the class initializer.
> I already considerate this one, but I don't like it because it is not
> correct in terms of the object-oriented concept.

Why?  I thought combining state/data and related functions into one object
is a key concept of OOP.

Ciao,
	Marc 'BlackJack' Rintsch