OpenEuphoria

1. problems with 4.0.3

• Posted by useless Oct 08, 2011
• 1200 views

I tried again to switch from euphoria 40b4-3412, which i have been using for some time now, to v4.0.3. I ran into two problems, one of which will stop me from ever using v4.0.3. And both problems have occured on two computers.

Problem one is when tracing a program using v4.0.3, i cannot F1/F2 to see the output of puts(1,"blarg"). Nothing happens when pressing any function keys. This puts a significant dent in tracing.

Problem two is remove_all() doesn't, on v40b4-3412 or on v4.0.3.

 
 
-- test the idiot remove_all() 
 
with trace 
 
include std\sequence.e 
 
object data 
 
trace(1) 
 
data = "<a href=\"?selectlang=ru\"><img>" 
puts(1,data&"\n") 
-- <a href="?selectlang=ru"><img> 
-- cannot F1 or F2 here, nothing happens,  
-- i cannot see the puts in 4.0.3 
-- i CAN see the puts in 40b4-3412 
 
data = remove_all("?selectlang=ru",data) 
puts(1,data&"\n") 
-- <a href="?selectlang=ru"><img> 
-- cannot F1 or F2 here, nothing happens,  
-- i cannot see the puts in 4.0.3 
-- i CAN see the puts in 40b4-3412 
-- but data still contains "?selectlang=ru" 
 
abort(0) -- something to end the trace on 
 

But this works fine on both versions:

     place1 = match("?selectlang=ru",data) 
     while place1 do 
       data = data[1..place1-1] & data[place1+14..$] 
       place1 = match("?selectlang=ru",data) 
     end while 

What i want to end up with in the example above is:

data = "<a href=\""><img>"

useless

3. Re: problems with 4.0.3

• Posted by jimcbrown (admin) Oct 08, 2011
• 1263 views

Looking at http://openeuphoria.org/forum/m/116090.wc message:116090 the binary build of 4.0.3 for W32 that was released - despite the fact that it was built with Watcom - had a known issue with keyboard handling.

You later said the same thing at http://openeuphoria.org/forum/m/116411.wc message:116411 which makes me suspect that you believe this is an occurance of the same bug.

Unless someone has updated the binary release of W32 4.0.3 since then, it's necessary to build Euphoria from the source code with Watcom to avoid this issue.

5. Re: problems with 4.0.3

• Posted by jimcbrown (admin) Oct 08, 2011
• 1133 views

public function remove_match(object needle, sequence haystack) 

Wait, can't find_replace() / match_replace() do this?

7. Re: problems with 4.0.3

• Posted by DerekParnell (admin) Oct 08, 2011
• 1115 views

Oops ... so they can. I totally forgot about these. We need to improve the documentation cross references for similar functions.

Kat, this should work for you ...

include std/search.e 
data = match_replace("?selectlang=ru", data, "") 

9. Re: problems with 4.0.3

• Posted by useless Oct 09, 2011
• 1052 views

I was somewhat thrown off by the use of the word "element". While i know Euphoric atoms and sequences, i interpreted "element" as a collection of atoms like "blagtorf", as opposed to a collection of sequences like {"blag","torf"}.

I wonder if sub-naming functions for what they operate on would be handy. So replace_all_s() and replace_all_a(). I don't know. I do think it's shortsighted to lock in a function name to atoms or sequences, when it's an equally great name for the other. Since the implementation of the function calls everything an object, why not sprinkle a few if sequence(needle) or if atom(needle) and handling the values differently?

useless