• 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: App Supplied Coercion?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: App Supplied Coercion?


  • Subject: Re: App Supplied Coercion?
  • From: Bryan <email@hidden>
  • Date: Thu, 02 Aug 2001 14:07:24 -0400
  • Organization: Apex Radiology

Personally, I find the automated coercions to be one of the strong points in
AppleScript.

At least, it is for us of the Eanglish tongue.

In our conversational interaction (which is our most common form of use;)
we routinely imply the class of a term by it's context.

It's most convenient to be able to code the same way.

As in the spoken language, there are occasional misdirections of intent as a
result.

Bryan Kaufman



Paul Berkowitz wrote:

> On 8/2/01 3:17 AM, "Ehsan Saffari" <email@hidden> wrote:
>
> > Hi
> >
> > In various AS sources it is pointed out that applications, as well as
> > osaxen, may provide coercions. Anyone know of an application that does
> > so? Finder maybe? And if an app does do it, how does one go about finding
> > out what coercions are provided, any particular resource to check?
> >
>
> As far as I can see, all applications which implement the 'save' command
> from the Standard Suite - and which incorrectly and improperly state 'in
> [alias]' as the class type for the 'in' parameter in their Dictionaries
> except for a few new OS X apps (TextEdit, Mail and OmniWeb) which correctly
> state 'in [string]' - are in fact coercing 'string' to 'file specification'.
>
> It's pretty clear that the incorrect '[alias]' terminology must have been
> taken from a faulty Apple SDK, and which Apple has at last corrected in some
> of their new apps for OS X - perhaps even in a new SDK too since OmniWeb has
> got it right. (Some of the Apple OS X apps, such as QuickTime 5, still have
> it wrong). But I'm quite interested in understanding what sort of coercion
> is actually taking place - it certainly _looks_ like a
> string-to-file-specification coercion. Can Chris Nebel or anyone else (Jon
> Pugh?) explain?
>
> --
> Paul Berkowitz
> _______________________________________________
> applescript-users mailing list
> email@hidden
> http://www.lists.apple.com/mailman/listinfo/applescript-users


References: 
 >Re: App Supplied Coercion? (From: Paul Berkowitz <email@hidden>)

  • Prev by Date: URL Access Scripting, error 3259?
  • Next by Date: Re: Apple Data Detectors....
  • Previous by thread: Re: App Supplied Coercion?
  • Next by thread: Re: App Supplied Coercion?
  • Index(es):
    • Date
    • Thread