Re: [dylan] [archeology] locked vs atomic

Does 'define locked variable' actually take a lock?

Personally I dislike the idea of making it easy to take
locks on tiny things like variables and slots. It's expensive,
prone to deadlock, composes poorly, etc etc.

It seems to me that we should provide locks (we do)
and have a memory model that does atomic updates
to "atoms". That is, lose both adjectives!

For what it's what, that's not what I thought 16 years ago.

--Scott


On Sun, Nov 25, 2012 at 7:18 PM, Bruce Mitchener
<[email protected]>wrote:

> This is going back into some ancient history ...
>
> OpenDylan supports "define locked variable" (for use with atomic
> operations). However, it also supports "define atomic variable", however,
> nothing actually uses that adjective.
>
> Similarly, there is the start of some support for "atomic slot", but not
> "locked slot".
>
> Does anyone recall what the "atomic variable" and "atomic slot" were
> intended to be and how they compared with "locked variable"?
>
> This goes back to 1996 or so ...
>
> Thanks!
>
>  - Bruce
>
>
> _______________________________________________
> hackers mailing list
> [email protected]
> https://lists.opendylan.org/mailman/listinfo/hackers
>
>

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers