Re: Images and libraries

ragofu64@[EMAIL PROTECTED]
 wrote:
> On 29 mar, 13:05, Doug Hoffman <no.spam> wrote:
> 
> 
>> My guess is that no one is using it to create applications.  One reason
>> for this would be the problem of getting objects.fs to run in a
>> non-source, or turnkey, application.
>>
> 
> Guess wrong :-)
> 
> I am using it ( a VFX for Linux ****ting ).
> Most of the time I use dynamically allocated objects.
> I have no need to name them, only a few and
> I don't need to save any persistent state.

By "application" I mean non-source programs for other people 
(non-programmers) to use.  If you have done that, great.  Is it 
something I could download and look at?


> By the way, I have discovered that objects.fs is not thread-afe,
> even with a cooperative multitasker.
> 
> The current implementation of the 'this' pointer uses a VALUE, shared
> by all tasks.
> This has given me lots of hours of headaches. I have changed to the
> alternate implementation
> written in the comments, but using a USER variable instead. Problem
> solved.
> Conclussion: any serious OOP package should be thread-safe :-)

Thanks for the warning.

Did you do anything to safely catch the error when sending an 
unrecognized message?  As it is objects.fs will simply crash my Forth. 
I would want to add a safe check (which would slow down the late binding).

-Doug