• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]


  • Subject: Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
  • From: Steven Angier <email@hidden>
  • Date: Tue, 01 Oct 2002 11:54:09 +1000

On 1/10/02 2:47 AM, "has" <email@hidden> wrote:

> Shane Stanley also wrote:
>
>
>>> BTW, I'm reading this at the moment:
>>> <http://www.mip.sdu.dk/~mik/papers/oo-languages.pdf>, which talks of the
>>> difficulty in transitioning practised procedural programmers-thinkers to
>>> OOD/OOP, and how to solve it (basically, by starting with OO in the first
>>> place). Good stuff, makes a lot of sense.
>>
>> Actually, that sentence -- that the solution to the difficulty of
>> "transitioning" people who think one way to think another is to start them
>> with another way in the first place -- is a fine example of something that
>> makes no sense at all.
>
> Quite. I shouldn't have said "solve"; that was totally misleading. I
> should've said "avoid". If folk don't learn procedural coding to begin
> with, they won't have any preconceptions (baggage) to hinder them when they
> come to learning OOP. Ergo, there IS NO paradigm-shift problem to be dealt
> with.
>
>
> In other words, you only get one shot at a clean slate, so make sure it's
> the one that's most appropriate. For folk who only ever want to do simple
> things in AS, learning OOP is really overkill. But for folk who know they
> want to go beyond basic tasks into stuff like workflow systems, starting
> with OOP is going to pay off far better than starting with procedural and
> then trying to transition once procedural gets too painful to bear.

Let's not confuse OOD with OOP -- two very different things.

I am a procedural programmer -- as that is the style I am most comfortable
with -- but my application/workflow designs are very much object-oriented.


Steven Angier
Macscript.com
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
  • Next by Date: Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
  • Previous by thread: Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
  • Next by thread: Re: "difficulties in OO" [was Re: Adobe's lousy AppleScript implementations]
  • Index(es):
    • Date
    • Thread