OpenEuphoria

I expected that this would work:

sequence m = { 10, 20 } 
{ m[1], m[2] } = { m[2], m[1] } 
? m 

Instead I get:

<0132>:: Syntax error - expected to see possibly ',', not '[' 
{ m[1], m[2] } = { m[2], m[1] } 
   ^ 

Using one of the 4.1 recently available:

Euphoria Interpreter v4.1.0 development 
   32-bit Linux, Using System Memory 
   Revision Date: 2014-01-11 22:35:01, Id: 5777:944d3dd7b349 

_tom

Hallo

Eu4.1 isn't released also Eu4.0.6 isnt't released yet (as far as i know...)
but me (and other people, see: http://openeuphoria.org/forum/123547.wc?last_id=123579 )
have built testversions from the Mercurial Repo.

Today i have uploaded the htmldocs so you can read them.

See Sections 9.2 9.3 for bugfixes and new features.

See Section 4.9 in the struct branch for this new feature.

See: http://euphoria.indonesianet.de/eu4zip.html

(I did this real quickly, hopefully everything works like expected.)

Maybe, soemone can add the list of bugfixes and new features somewhere on the OpenEuphoria Website.

Andreas

Hallo

Sorry, I'am not a developer of OpenEuphoria nor I'am involved in writing the docs
I just made the current status of OpenEuphoria, easily public available.

I do not even know if the developers like what i have done. I just did it.

For sure most of the 4.1 docs are the same than the 4.0 docs, why should they through them away? if there are the same?
It's the same code base.

Andreas

There isn't, AFAIK. We discussed this, but the conclusion was very discouraging: http://openeuphoria.org/forum/m/119179.wc

Due to the code freeze, this will have to wait until 4.1.1

The latest version of the 4.1 docs was definitely uploaded: http://euphoria.indonesianet.de/eu4zip/doc41/html/release_4_1_0.html#_6653_version410datetbd

I'm not sure how you could have missed these.

I did not miss them,

i have not seen the data on 4.1, because you didn't upload the 4.1 docs.

but they did not contain the DLL unload, which should be in 4.1,

because Matt did fix the memory leak.

I believe Matt fixed the problems. However, i lost the code he last supplied, and has never responded about it on irc when i asked.

Regarding the DLL leaks, the last pastey i see on it is http://openeuphoria.org/pastey/157.wc and we discussed it on irc at 5am on Monday 10/1/2012.

Then Tuesday 10/2/2012,
[15:13] <katsmeow-afk> if someone like myself and raseu, and maybe Greg, were to know the max size of the dlls we wish to load-unload, can eu make a memory hole in itself so no memory allocation would be needed to load-unload thse dlls?

And then nothing. Since Nov 2nd 2012. But i am pretty sure Matt did fix the unload memory leak.

09:50 <@mattlewis> no more leaks: http://openeuphoria.org/pastey/157.wc#3101 
10:06 <@iamlost> mattlewis: :( 
10:06 <@iamlost> mattlewis: ): 
10:07 <@mattlewis> ? 
10:08 <@iamlost> mattlewis: there's still no way to do that automagically 
10:09 <@iamlost> each individual shared object must be hand edited 
10:09 <@mattlewis> yeah, the translator needs to be updated 
10:10 <@mattlewis> also, that doesn't release all of the top level objects that 
12:40 <@mattlewis> err....now I remember why we can't deref all vars at the end 
12:40 <@mattlewis> delete_routine()s may end up accessing freed vars 
12:42 <@katsmeow-afk> then have the delete_routine() free the vars 
13:38 <@mattlewis> eh...hmmm..... 

11:58 <@mattlewis> hmm...several files in the std library allocate some memory