HyperCard Mailing List

[HC] More flexible HyperTalk syntax (LiveCode)
(Msg 1 of 2)
Uli Kusterer <Witness.of.TeachText@[redacted].net>
Sunday, 03-Feb-2013 20:07 GMT
The LiveCode boss just blogged about what they call 'Open Language':

http://blog.runrev.com/blog/bid/265511/

Essentially, they want to add support for more English-like syntax for XCMDs, and also use that to modularize LiveCode. I'm glad someone whose day job it is to write an xTalk finally goes in that direction (though, being me, I'm wondering 'why limit this to XCMDs').

It is definitely an improvement over LiveCode and SuperCard's tendency to just bundle or integrate XCMDs with XCMD syntax. I hope that the least that comes out of this is xTalks returning to their root as a language with English-like syntax.

Sadly, a lot of the comments go off on tangents, suggesting stuff like getting rid of xTalk altogether (Didn't we already do that when Lingo morphed into Flash?).

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
[HC] More flexible HyperTalk syntax (LiveCode)
(Msg 2 of 2)
J. Landman Gay <jacque@[redacted].com>
Sunday, 03-Feb-2013 21:43 GMT
On 2/3/13 2:07 PM, Uli Kusterer wrote:
> The LiveCode boss just blogged about what they call 'Open Language':
>
> http://blog.runrev.com/blog/bid/265511/
>
> Essentially, they want to add support for more English-like syntax
> for XCMDs, and also use that to modularize LiveCode. I'm glad someone
> whose day job it is to write an xTalk finally goes in that direction
> (though, being me, I'm wondering 'why limit this to XCMDs').

As I understand it, XCMDs wouldn't even be needed any more after Open
Language is implemented except in some rare cases. Open Language
consists of definition files can point to script collections written in
xtalk or C or anything else.

But I'm not as techy as Mark Waddingham or as you, so I could be confused.

--
Jacqueline Landman Gay | jacque@[redacted].comHyperActive Software | http://www.hyperactivesw.com
HyperCard® and HyperTalk™ remain trademarks of Apple, Inc.; other trademarked products and terms mentioned in this archive are the property of their respective trademark holders. Individual messages remain the intellectual property of their respective authors.