On 2015-03-23 20:41, Michael Doub wrote:
I am still trying to figure out how the "bind to ... " works. Some
where there has to be a linkage between this "bind" step and the OS
level library, So at run time, the library is loaded into memory and
the final address resolution takes place.
This i
Richmond,
This maybe the blind leading the blind, but here is my take. Hopefully
someone will correct me.
Take a look at ~/livecode/libscript/src/foreign.mlc. Here is where
foreign types are defined.
Now take a look at ~/livecode/libscript/src/math.mlcNote that "use
com.livecode.fore
On 23/03/15 12:30, Peter TB Brett wrote:
On 2015-03-22 22:59, Peter W A Wood wrote:
Richmond
I believe that Richard’s “providing OS API access” is a
simplification, probably an over simplification, of “providing the
ability to access the OS API”. As I understand, LiveCode Builder will
allow us
Thanks, Peter
> On 23 Mar 2015, at 18:30, Peter TB Brett wrote:
>
> On 2015-03-22 22:59, Peter W A Wood wrote:
>> Richmond
>> I believe that Richard’s “providing OS API access” is a
>> simplification, probably an over simplification, of “providing the
>> ability to access the OS API”. As I under
On 2015-03-22 22:59, Peter W A Wood wrote:
Richmond
I believe that Richard’s “providing OS API access” is a
simplification, probably an over simplification, of “providing the
ability to access the OS API”. As I understand, LiveCode Builder will
allow us to write code which can directly call an O
Richmond
I believe that Richard’s “providing OS API access” is a simplification,
probably an over simplification, of “providing the ability to access the OS
API”. As I understand, LiveCode Builder will allow us to write code which can
directly call an OS API but, of course, we will need to defi
