Jan Vrany <jan.vrany@fit.cvut.cz> [Mon, 22 May 2017 22:13:27 +0000] rev 3774
Merge
Claus Gittinger <cg@exept.de> [Tue, 07 Feb 2017 13:48:18 +0100] rev 3773
#DOCUMENTATION by cg
class: JavaMonitor
comment/format in:
#decrement
#increment
#reinitCounter
#reinitCounter:
changed:
#disableWait
#enableWait
#initialize
#waitEnabled
(grafted from 27d34a8a6315377a6a5bd60b37ac5163c64f059d)
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 04 May 2017 23:54:12 +0200] rev 3772
Merge
Jan Vrany <jan.vrany@fit.cvut.cz> [Sat, 18 Mar 2017 22:18:19 +0000] rev 3771
Issue #94 [4/x]: Added some benchmarks for thinlocks
Jan Vrany <jan.vrany@fit.cvut.cz> [Thu, 29 Dec 2016 21:48:21 +0000] rev 3770
Issue #94 [3/x]: Use new thinlock implementation
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 09 Dec 2016 00:25:36 +0000] rev 3769
Merge
Jan Vrany <jan.vrany@fit.cvut.cz> [Fri, 14 Oct 2016 22:21:46 +0100] rev 3768
Issue #94 [2/x]: Remove _lockWord_ instvar from JavaBehavior
...as it is no longer needed.
https://swing.fit.cvut.cz/projects/stx-libjava/ticket/94
Jan Vrany <jan.vrany@fit.cvut.cz> [Wed, 12 Oct 2016 00:14:35 +0100] rev 3767
Issue #94 [1/x]: Introduce a `lock` instance variable to JavaBehavior and synchronize on it.
...when execution synchronized static methods as well as classinit
synchronization. The `lock` keeps a `java.lang.Object` created for
locking purposes only. This will allow to simplify `monitorenter()`
/ `monitorexit()` implementation as it would need not to check whether
it's dealing with `java.lang.Object` (sub)instance or `JavaClass`.
https://swing.fit.cvut.cz/projects/stx-libjava/ticket/94
Claus Gittinger <cg@exept.de> [Wed, 30 May 2018 19:52:13 +0200] rev 3766
*** empty log message ***
Claus Gittinger <cg@exept.de> [Fri, 25 May 2018 13:13:33 +0200] rev 3765
#FEATURE by cg
class: GroovySourceHighlighter
added: #formatFileContents:elementsInto:using:
changed: #format:
class: GroovySourceHighlighter class
added: #formatFileContents:elementsInto: