• 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: Passing *possible* variables to a handler
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Passing *possible* variables to a handler


  • Subject: Re: Passing *possible* variables to a handler
  • From: "Arthur J. Knapp" <email@hidden>
  • Date: Mon, 15 Jul 2002 17:44:43 -0400

> Date: Mon, 15 Jul 2002 10:42:38 +0100
> From: has <email@hidden>
> Subject: Re: Passing *possible* variables to a handler


> Arthur J. Knapp wrote:
>> I also like the possibilities this brings up

> [Uh-oh, here he goes again... <smak> Bad Hamish! Not before Arthur's taken
> his medicine.;p]

>> for wrapping other object-
>> like data types:
>>
>> on newDateTime(_optional_date_)

> Well yes, but remember what I said already about this stuff not being all
> that good as a direct replacement for existing data types. Use in
> moderation, and make sure you document why you've done it and where
> behaviour differs from the expected. It may still be better to roll your
> own objects from the ground up in 99% of cases, hiding state completely and
> providing access via your own methods only. Then there's no chance of
> confusion over how the object should and should not be used.

Sure, but in a fully work-out and documented environment, this provides
for a very natural extension to working with an existing data type:

set extendedDate to newDateTime(current date)

extendedDate's day --> an old syntactic friend

extendedDate's day0 --> a new syntactic friend

While I appreciate that you were looking for a new means of speeding
things up, a la Serge, I really like the new possibilites in terms of
trying to seamlessly add to the functionality of existing data types.


> OTOH, AS is such a weeeeird language for doing OOP in, I doubt there's much
> we could do to make it any weirder. (Please don't take that as a challenge,
> however.;p)

What, oh, sorry, I wasn't listening. I have too many weird things to
come up with...

;-)

{ Arthur J. Knapp, of <http://www.STELLARViSIONs.com>
a r t h u r @ s t e l l a r v i s i o n s . c o m
}
_______________________________________________
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: Solving equations (was Re: Unquoting a string)
  • Next by Date: Re: Label index
  • Previous by thread: Re: Passing *possible* variables to a handler
  • Next by thread: Re: Passing *possible* variables to a handler
  • Index(es):
    • Date
    • Thread