Path: csiph.com!news.mixmin.net!news.albasani.net!.POSTED!not-for-mail
From: j4n bur53 <janburse@fastmail.fm>
Newsgroups: comp.lang.java.programmer
Subject: Re: Library for Escalable Locks, Slimmest API?
Date: Sun, 14 Aug 2016 11:50:00 +0200
Organization: albasani.net
Lines: 12
Message-ID: <nopes8$f45$1@news.albasani.net>
References: <no7p5p$11i$1@news.albasani.net> <slrnnqfmvf.456.avl@login.logic.tuwien.ac.at> <no9cu2$1pl$1@news.albasani.net> <slrnnqmf45.456.avl@login.logic.tuwien.ac.at> <nofjbk$sgd$1@news.albasani.net> <26c75c11-5955-45a6-919d-3de1255c9c15@googlegroups.com> <nohksl$lsj$1@news.albasani.net> <e16p89FdmcoU1@mid.individual.net> <nompol$fqt$1@news.albasani.net> <e19h9vF37j0U1@mid.individual.net> <nopee6$efa$1@news.albasani.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.albasani.net KSIZFfbERQEAOWhYxTvSW00mXOU0Y8JhLLXqFLQS2Ow1urBf1ausF9xkJ5sKLLfLIgu3L0uOl9sU7LtRWqD2LxDWAC45tQca0bHRRhz/1DwcqSXqOBWhp+jJ1YAG7V6J
NNTP-Posting-Date: Sun, 14 Aug 2016 09:50:00 +0000 (UTC)
Injection-Info: news.albasani.net; logging-data="WiOIqz1mW3o39Fuue82YQNCweh2iVgNH/bhKEP1Lgp4JQOcmSkFjN3Vgb/y1UINuH27oa1nFlYNuIL6i9Mdof1VOs1PEaib9O4qvpiM156fVGhL6RuPsktVtOQWWDWn2"; mail-complaints-to="abuse@albasani.net"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
In-Reply-To: <nopee6$efa$1@news.albasani.net>
Cancel-Lock: sha1:EQQ2dw42GryePfKa3Os1/Qi8v1Q=
Xref: csiph.com comp.lang.java.programmer:35319

j4n bur53 schrieb:
> Currently it is possible that a thread that does not do
> the loading of the Prolog text, will see how a predicate
> gradually is loaded. The new read lock will prevent this.

BTW: The Erlang loader can do such things, block
a predicate until a module is re-loaded. Erlang is
a little bit the inspiration for my new loader.

Ordinary Java cannot do it, class loading is usually
serialized by a single lock. But there are also
parallel class loader options around.