Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!grobbins From: grobbins@Apple.COM (Grobbins) Newsgroups: comp.sys.mac.hypercard Subject: Re: Confused Novice Message-ID: <53044@apple.Apple.COM> Date: 18 May 91 06:57:16 GMT References: <3586@spim.mips.COM> <53006@apple.Apple.COM> <424@aplcomm.JHUAPL.EDU> Organization: Apple Computer Inc., Cupertino, CA Lines: 48 In article <424@aplcomm.JHUAPL.EDU> john@aplcomm.jhuapl.edu (John Hayes) writes: > I am a Hypertalk novice and I find myself baffled by its syntax. >I frequently type in reasonable looking code; when it doesn't work >I rarely understand why and must resort to experimentation to make it >work. There are rules, but their similarity to English is sinister rather than helpful for scripters. >-- this doesn't work >put the id of card into placeHolder "card" isn't sufficient to specify the object. These are better: this card third card the third card card 3 card "frump" card id 5713 Only objects which are truly unique, like msg and HyperCard, are used without a name, id number, or ordinal. >-- this works >get the id of card >put it into placeHolder HyperTalk will stretch to understand you, and this can cause confusion. If you end a line with "of card" or "of background" HyperCard will assume you meant "of this card" or "of this background". But "of card" and "of background" are not proper identifiers, and HyperCard really should consistently reject them. Generally you will have to identify cards, backgrounds, and other objects with a name, id number, or ordinal. > I am an experienced programmer and know many languages, but I >continually come up against problems like the one above. Can anyone >recommend a book that accurately and completely describes the syntax >and semantics of Hypertalk? The most sophisticated and frank published account I've seen is "HyperTalk 2.0: The Book" by Winkler and Kamins. The Claris manual is a tad more complete as a reference of keywords, however. Grobbins grobbins@apple.com Usual disclaimers apply.