> 2) I suppose that the garbage collector would have to keep track of > all those CELL pointers in the array, that are outside of the reach of > the picolisp symbol table. That would be the price to pay, I think > a smaller price than adding another datatype. > > One cheap workaround for this would simply be to have a "nogc" function that temporarily disables the GC around a piece of code. If you're crunching data in arrays, you probably want to isolate that operation in its own little high-performance block anyway.
- A pragmatic solution to using arrays in picolisp Enrique Sánchez
- Re: A pragmatic solution to using arrays in picol... Alex Gilding
- Re: A pragmatic solution to using arrays in p... Enrique Sánchez
- Re: A pragmatic solution to using arrays in picol... Alexander Burger
- Re: A pragmatic solution to using arrays in p... Enrique Sánchez
- Re: A pragmatic solution to using arrays in p... Enrique Sánchez
- RE: A pragmatic solution to using arrays ... Denis Fourt
- Re: A pragmatic solution to using arr... Yiorgos Adamopoulos
- Re: A pragmatic solution to using arrays ... Alexander Burger
- Re: A pragmatic solution to using arr... Enrique Sánchez
- Re: A pragmatic solution to usin... Michel Pelletier
- Re: A pragmatic solution to ... Mansur Mamkin