Describing LiveCode

[JB]

On Aug 11, 2015, at 12:20 PM, Richmond <richmondmathewson at gmail.com> wrote:

> I'm not that interested, as, at the moment, at least, LiveCode does almost all that I require (let's leave communicating
> back-and-forth between USB devices out of this discussion).
> 
> What I am interested in is how to communicate adequately to people who have grown up with 3G languages the
> very great advantages (particularly from a pedagogical point of view) of LiveCode.
> 
> While the C++ book I bought makes interesting reading, in parts, I cannot see myself bothering to learn to code
> anything beyond the most pedestrian stuff in it: even if for the simple reason that all that bother about
> "/edit, preprocess, compile, link, load/ and /execute/" gives me the willies.
> 
> In fact, thinking about "/edit, preprocess, compile, link, load/ and /execute/" I really wonder what RunRev think they are doing,
> as the lack of all the fiddly stuff is half of what makes LiveCode so much better. RunRev's propaganda machine hasn't got off the ground!
> 
> Richmond.

LiveCode will be allowing the use of pointers and that is what your old school C++
parents who talk about object-oreinted programming are referring to.  They point to
a place in memory.  These old schoolers will probably love the fact Livecode will be
able to use these things without compiling.

John Balgenorth