[e-lang] Some minor bugs (switch and traceln)

[Thomas Leonard]

On Fri, 2010-02-12 at 12:04 -0500, Kevin Reid wrote:
> On Feb 12, 2010, at 11:25, Thomas Leonard wrote:
> 
> > A couple of minor bugs:
> >
> > When there is no match for a switch statement, the expansion
> > (ENodeBuilder.switchx) is:
> >
> >  throw("no match: " + temp)
[...]
> This should be fixed by changing the expansion to
> 
>    throw("no match: " + E.toQuote(temp))
> 
> If you could provide a patch for this and/or the line wrapping bug,  
> I'll check and commit it.

I've committed the fixes to a new "proposed" branch. If you have a Git
clone of the svn repository (made with the command I sent earlier), you
should be able to review and commit like this:

# Download Thomas's "proposed" branch... 
git pull git://gitorious.org/~tal-itinnov/repo-roscidus/it-innovation.git proposed

# See what he changed, relative to the svn copy...
git log -p git-svn..

# Push changes to svn... (or use --dry-run to see what would happen)
git svn dcommit


Otherwise, the patches can be seen in a browser here:

http://gitorious.org/~tal-itinnov/repo-roscidus/it-innovation/commits/proposed

> Also, MarkM and I have agreed you ought to have commit access; the  
> only reason you don't yet is that we haven't been able to contact Dean  
> to get you added to the password file. (Yes, yes, DVCS is better and  
> all that.)

Thanks, though I'd prefer having someone review and comment on my
changes, as I'm not still not that familiar with the code.

On a related note, I'm updating the Walnut guide on the wiki to answer
questions from co-workers. I'm writing the new text as if I know what
I'm talking about, and relying on you guys to fix it...

(but I can't update it at the moment because I get the error "Could not
open socket")


> (By the way, if the tracelog is showing intermixed with your regular  
> IO, and you haven't done this on purpose or are using devrune, then  
> your E is misconfigured or has a bug.)

I put this in my ~/.e/user-eprops.txt:

  TraceLog_dir=-
  e.onErrorExit=report

I think most people here are using these options. Not being able to see
errors easily, and having to press Return after getting one, were the
two main complaints people had when they started using E.

But, even if the trace messages were going to a file, I'd still rather
have them wrapped by my text editor, to the width of the window.

Thanks,


-- 
Dr Thomas Leonard
IT Innovation Centre
2 Venture Road
Southampton
Hampshire SO16 7NP

Tel: +44 0 23 8076 0834
Fax: +44 0 23 8076 0833
mailto:tal at it-innovation.soton.ac.uk
http://www.it-innovation.soton.ac.uk