I put up on sf.net new Windows binaries for Unicon 11.9 (named it 11.9.1).
This is basically a non-concurrent release (no thread support) that has all
of the bug fixes applied to Unicon 12.0. Presumably it doesn't require any
DLLs to run.

Just in case someone like non-concurrent Unicon better or having trouble
running the concurrent version (we would love to have bugs reports in that
case!)

Cheers,
Jafar



On Thu, Jul 14, 2011 at 1:05 AM, Jafar Al-Gharaibeh <to.ja...@gmail.com>wrote:

> Hi,
>
>  A new non-beta Unicon Version 12.0 with concurrency support for Windows is
> now available for download at :
>
>    https://sourceforge.net/projects/unicon/
>
> This is the default download now replacing Version 11.9 but you can still
> access several old releases at:
>
> https://sourceforge.net/projects/unicon/files/
>
> Here are some of the the bug fixes (We are still working on the recent
> Windows issues) and new features
>
> ***   Several bug fixes including fixes for &error and &trace
>
> ***   New syntax for critical regions / mutexes
>
>         critical x expr      # where x is a mutex. The expression expr is
> serialized on x
>
>    this is equivalent to:
>
>            lock(x)
>            expr
>            unlock(x)
>
>    ex:   assuming  a mutex was initialize with :   region:=mutex()
>           this is how "critical" can be used
>
>            critical region counter +:=1
>
>    Be aware of that fact that breaking out of expr  doesn't automatically
> unlock x.
>    It is the programmer responsibility to do so.
>
> *** The join() function is pending for removal in favor of merging with
> wait().
>    For now join(thread_co) is equivalent to wait(thread_co).
>    Both functions block the calling thread until the thread thread_co
> finishes.
>
> *** The thread() function was extended with two optional parameters to give
> control over the
>      initial size of the string and block regions for the new thread. This
> is would be particularly
>      useful if you know the thread is doing (or NOT) a lot of memory
> allocation. Another case
>      is when the you create tens, hundred or even thousands of threads
> (Thanks to your "exploding" examples Steve! :) ) . In that case small size
> regions would
>      be a good idea.
>
>     thread(co-exp, blocksize,stringsize)
>
>   ex:
>
>    thread(co,  2*1024*1024, 1024*1024 ). # fire co as a thread and give it
> 2MB for the block region and 1MB for the string region.
>
>     By default new threads allocate regions with size equals to 25% of the
> main thread regions sizes.
>
> *** Optimized code that runs about 10% faster.
>
> Hopefully we will have another release in few weeks addressing the recent
> Windows bug reports.
> Thanks for everybody specially those who helped us identify/fix the bugs.
>
> Cheers,
> Jafar
>
>
>
>


-- 
"Let there be no compulsion in religion: Truth stands out clear from error"
[The Holy Qur'an 2:256]

"Injustice anywhere is a threat to justice everywhere"    Dr. King
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on "Lean Startup 
Secrets Revealed." This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Reply via email to