Re: [sc-dev] interpreter issues

["felix" <felix@xxxxxxxxxxxxxxxxxxx>]

since the timing is now mostly handled by the server, we just have to keep a step ahead of NOW and slot our requests into the server:
so perhaps our dependancy on a really strict time base in the lang has abated ?
i haven't gotten down to day to day scheduling; but it seems to me that i could be satisfied with a looser timing backbone on the lang side:

not that im rushing to drop sclang:
not at all:



> Hi all,
> 
>   I certainly agree that it would be nice to use a control interpreter
> that has a large user base.  The problem is that everytime I investigate
> the matter it turns out that the interpreter is poorly equipped for real
> time performance.  The SC interpreter (perhaps PyrTalk would be a name for
> it) has constant time method look up and pause free garbage collection.  I
> have heard that the Java gc is "much improved" but am not aware of any
> version that is truly realtime. Am I wrong?  
> 
>  Anyway, if it turns out that the SC interpreter has unique features, it
> might make sense to try to put together a version of the interpreter alone
> as a scripting tool to generate a larger user base.
> 
> 
> RJK
> 
> 
> _______________________________________________
> sc-dev mailing list
> sc-dev@xxxxxxxxxxxxxxx
> http://www.create.ucsb.edu/mailman/listinfo/sc-dev
> 
> 
> 

http://crucial-systems.com