Re: Object Oriented simpleton design pattern<g>

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"MP" <NoSpam@xxxxxxxxxx> wrote in message
news:OdFVnkBiHHA.1624@xxxxxxxxxxxxxxxxxxxxxxx

"Max Kudrenko" <vb_mvp@xxxxxxxxxxx> wrote in message
news:1177578856.772406.316790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Mark,

My thoughts on this:
1) Yes, OOP is really beneficial for bigger projects only. For small
utilities you have, procedural approach is still the quickest and
cheapest and this is exactly where the classic VB shines.
2) VB isn't really an OO language and so won't help in properly
practicing it. You can rewrite all your code in classes but still,
they are not real OO classes. Perhaps, the classes way will be tidier
and more marketable if you want to sell it but it won't give you any
other benefits including performance.

Hope this helps,

Max Kudrenko
Brainbench MVP Program for Visual Basic
www.brainbench.com



Thanks Max for your response,
as I mentioned, I realize oo is not req'd for something so small, just
trying to use a small example as a way to begin learning how to apply oo
to
more significant efforts

which language do you recommend for real OO?

Thanks
Mark


While this is not addressed to me, I'll add my little rant anyway. <g>

OO is never 'required' for anything. It just makes everything easier on the
long run. One can simplify small projects by merely changing where one
places the implementation (ie, less objects). But you'll find in VB you
always have one or using the services of one. VB is for "real" OO.

VB is a limited OOPL when compared to other OOPLs, such as C++ or dotNet.
But that doesn't make it less OO only that it doesn't have some mechanisms.

For example, in VB there is no compiler/runtime enforceable way to have a
Singleton or Static Members. That doesn't mean you can't create them. Or use
them. VB doesn't have implementation inheritance - but you can construct
objects that will appear identical to objects created using implementation
inheritance.

So your question should really be "what language do you recommend for the
most OOPL features"?

That would depend on the platform. But in general C++ wins over all. For MS
it would be VC++/CLI.

-ralph


.

Relevant Pages

  • Re: Object Oriented simpleton design pattern
    ... OOP is really beneficial for bigger projects only. ... VB isn't really an OO language and so won't help in properly ... An OOPL is useful in any size project. ... to do with "marketing" except in helping to deliver a more robust product. ...
    (microsoft.public.vb.general.discussion)
  • Re: Object Oriented simpleton design pattern
    ... OOP is really beneficial for bigger projects only. ... VB isn't really an OO language and so won't help in properly ... An OOPL is useful in any size project. ... to do with "marketing" except in helping to deliver a more robust product. ...
    (microsoft.public.vb.general.discussion)
  • Re: object-oriented programming explained in 51 lines
    ... Technically the most correct is that it is programming using an OOPL. ... any programming language that supports objects with identity that encapsulates properties and operations that collaborate using message passing as well as classes related by inheritance, polymorphism, and binding. ... Anything you can express in OOA/D model can be expressed in a procedural language, as full code generators for OOA models routinely do. ... Therefore there is no OO problem solution than cannot be implemented in both an OOPL and a procedural language. ...
    (comp.object)
  • Re: OOA?
    ... If the model is somehow executable, then the language is ... the model is *expressed* in an OOPL ... OO principles can only be applied in the context of an OO language. ... model that is fit for C++ and expect it to be fit for Smalltalk. ...
    (comp.object)
  • Re: development of C++ compiler
    ... So there should be nothing to prevent cross-compilation from an OOPL to non-OOPLs. ... subset) and use the not-mutable core language to build all concrete- ...
    (comp.object)