Re: Trace functionality, or lack thereof. (refers to String thread also)
- Posted by irv mullins <irvm at ellijay.com> Jun 01, 2004
- 472 views
Patrick Barnes wrote: > Problems I have with the trace system in Euphoria: > > 1. No way to see subscripts of sequences. "? myseq" works, but "? myseq[1]" > does not. > 2. No recursive references: "? myseq[i]" > 3. No real way to keep particular variables in view. > 4. No way to format sequences in a particular manner. > 5. No way to see function return values unless explicitly assigned to a > variable. > 6. Outdated DOS interface (Minor, but aesthetically ugly, and difficult to > use. > 7. Limited flow control (No way to "run until this point") > 8. (minor) Setting breakpoints "trace(1)" requires changing the source code, > and cannot be done in the trace window, or without messing up line numbers. > Perhaps offer an alternative method of having an external file .trc? which > could be generated by the tracer, or hand-written. > > Now, a fully-featured GUI debugger would be a very nice thing. Rob, I can > understand you're hard pressed keeping the Euphoria language regularly > updated, and don't really have the time to devote to a big project like > that. However, how about exposing the trace interface from the interpreter > to an external program? Bravo! These are all valid criticisms, and I especially like the idea of publishing the trace interface so someone other than RDS can write a fancy IDE/debugger. Sadly, I don't think it's likely to happen. Irv