Re: Trying to catch up

> > a good definition/specification is worth much more than > > hundreds lines of code which might need to be changed later > > a specification which is well planned makes the implementation > > later a piece of cake > > Perhap... but, imho, a proposal to have a specification is worth > nothing. yes you are definitely right > Do you have a > prototype for said definition/specification? if we could first agree on which classes are needed i will also write some specifications and implement stuff what i need currently and which should also make sense for many others are classes for ----writing logfiles from an application, error.log, etc. to keep track of my application, it's errors, etc. the problems might be to coordinate the multiple access if a hundreds of entries shall be made at once, because the application is highly frequented may be this class should work together with some exception/error class ----multilingual support, kind of like the LOCALES as known from java, although my main focus actually was intended to provide a class which automates translation, like i have a function called $translate->get(SOME_TEXT_CONSTANT); which then gets the text in the current language, which can be set before by using $translate->language = 'ISO constants for language' anyway i still think it makes sense to use a kind of class as provided by java (and extend it IF necessary) i would like to discuss here - what other classes are suggested - if we should stick to some other concept as the java concept? or some other language or library, as once was said here may be CPAN have fun Wolfram