Re: [q-lang-users] Complex numbers

[<bri...@co...>]

Just a note to point out that most of the CLR-based languages (examples: VB.NET, C#) have, in addition to standard garbage collection based on reachable roots of language objects, another, separate protocol for disposing of non-GC'd system resources like database locks, video-card contexts, midi channels. So there's an example of handling normal GC separately from this concern.

These languages typically offer a block-structuring thing, called "using" in VB [and I can't remember what it's called in C#], and any types that implement interface IDisposable get, well, disposed of when control leaves the block.

CLR has yet-another protocol called finalizers, but I don't use them, they interact strangely with the rest of the VM [they're executed at unpredictable times on different threads], and I don't remember much more about them (they're viewed with jaundiced eyes by most sophisticated CLR users). 



--
BBeckman http://weblogs.asp.net/brianbec http://data/tesla 
------------------------------------------------------------------------------------ 
| Type inference | Object initializers | Anonymous types | XML CRUD | 
| Extension members | LINQ | Relationships | Nested functions | 
| Nullable of T | Relaxed delegates | Dynamic identifiers | Duck typing | 
| Pattern matching | Contracts | AJAX | Iterators | 
| Continuations | REPL | Join Patterns | Transactions | 
| XML Streams | Code Literals | Morphisms | Embedded DSLs | 
------------------------------------------------------------------------------------

-------------- Original message -------------- 
From: Albert Graef <Dr....@t-...> 

> John Cowan wrote: 
> > I suppose we could bit-by-bit replace the entire Q-in-C system with 
> > a Q-in-Scheme system, compiler, interpreter, user program and all. 
> 
> Yes, that should be possible, but I'm probably not the one who is going 
> to do it. ;-) I'd rather like to bootstrap Q in Q once we have native 
> compilation. 
> 
> > It wouldn't need its own garbage collector any more 
> 
> I'm not sure about that. At least it would still need to do reference 
> counting, since I want objects encapsulating state to be cleaned up 
> (closing files, etc.) as soon as possible. This makes handling temporary 
> stateful objects much more convenient. 
> 
> > Chicken doesn't do native threads, though, only call/cc based ones. 
> 
> I guess that this would be a showstopper for me, with all the realtime 
> multimedia applications I'm doing. 
> 
> -- 
> Dr. Albert Gr"af 
> Dept. of Music-Informatics, University of Mainz, Germany 
> Email: Dr....@t-..., ag...@mu... 
> WWW: http://www.musikinformatik.uni-mainz.de/ag 
> 
> 
> _______________________________________________ 
> q-lang-users mailing list 
> q-l...@li... 
> https://lists.sourceforge.net/lists/listinfo/q-lang-users