1. "find_from" not colored in trace screen

This is regarding version 3.1.1 (I haven't used version 4.0).

No big deal, but I noticed in the trace screen that the built-in function "find_from()" is not identified by magenta as it should be. I see that this function is a relatively recent addition so maybe it was overlooked.

new topic     » topic index » view message » categorize

2. Re: "find_from" not colored in trace screen

Well I did say "no big deal", but 77 views and not one reply? Guess I won't bother next time.

new topic     » goto parent     » topic index » view message » categorize

3. Re: "find_from" not colored in trace screen

hacker said...

This is regarding version 3.1.1 (I haven't used version 4.0).

No big deal, but I noticed in the trace screen that the built-in function "find_from()" is not identified by magenta as it should be. I see that this function is a relatively recent addition so maybe it was overlooked.

hacker said...

Well I did say "no big deal", but 77 views and not one reply? Guess I won't bother next time.

Well:

r200 | mattlewis | 2007-08-30 13:07:33 -0400 (, 30  8 2007) | 1 line 
 
Added find_from, match_from to syntax coloring in trace window 

But:

r198 | robcraig | 2007-08-29 00:49:08 -0400 (, 29  8 2007) | 2 lines 
 
merged into trunk all the changes on the 3.1.1 branch, 
plus EQUALS fix in emit.e, and a fix to ed.ex 

So the bug you are reporting was fixed almost 2.5 years ago.... but simply never made it into the 3.1.1 branch.

Actually, I'm a bit confused, as I thought find_from() wasn't made a builtin until 4.0 and was a library function (written in eu code) before then...

new topic     » goto parent     » topic index » view message » categorize

4. Re: "find_from" not colored in trace screen

jimcbrown said...

Actually, I'm a bit confused, as I thought find_from() wasn't made a builtin until 4.0 and was a library function (written in eu code) before then...

I'm even more confused because I've got a version of keywords.e dated June 6, 2007 that has find_from in it.

But in any case, I don't think someone will be updating v3.x Euphoria to fix this now.

new topic     » goto parent     » topic index » view message » categorize

5. Re: "find_from" not colored in trace screen

jimcbrown said...

Actually, I'm a bit confused, as I thought find_from() wasn't made a builtin until 4.0 and was a library function (written in eu code) before then...

No, it became a built-in in 3.1. In 4.0, with default parameters, it became redundant, since the regular find() now takes an optional 'from' parameter that defaults to 1.

Matt

new topic     » goto parent     » topic index » view message » categorize

6. Re: "find_from" not colored in trace screen

Thanks guys for the reply.

So I take it that all versions prior to 4.0 are abandonware? shame, it would be handy to have the new "find()" incorporating "find_from()". Perhaps Rob Craig would do it if I ask him nicely.

new topic     » goto parent     » topic index » view message » categorize

7. Re: "find_from" not colored in trace screen

hacker said...

Thanks guys for the reply.

So I take it that all versions prior to 4.0 are abandonware? shame, it would be handy to have the new "find()" incorporating "find_from()". Perhaps Rob Craig would do it if I ask him nicely.

I can't speak for versions prior to 3.0, since those are proprietary. 3.0 was the first open source release. Anyone can update it or 3.1 or 3.1.1. I think you (or anyone else) will find it difficult to add default parameters into the code for 3.1.

There's no reason why someone couldn't do a 3.2 release, or something, but I'm not aware of anyone interested in doing that, which is what I think Jim's point was. If you found some serious bug, it might be worth doing a 3.1.2 release, but I wouldn't classify a built-in not being highlighted in the interactive trace to be a critical bug.

Matt

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu