bugs

[Davide Del Vento]

Folks,

I assume that the list of bugs on github is incomplete, right? I don't
understand bug #1 (yet) is it deal breaking? I wrote a comment to bug
#3. I also created labels, the idea is to label every bug with either:

workaround-available (probably won't get fixed now, since with a
different syntax you can get the same result, but keep it documented)
minor (we'll see if we'll fix it)
major (show stopper)
maybe others in between, if we think we need them

And then with other labels to identity where the bug belong, e.g.
clip, ptest, slyp, proteus, etc.

I'm tempted to write a bug for the {...} problem so we don't have to
remember that's buried in bugs #3 and/or #4 (and then make those
"possible duplicates" of the first one). What do you think?

Let me know if you want me to look at any bug right now, e.g. the
range bug (I saw it mentioned in several places, including here:
http://infomage.com/newsandevents.html) but I don't understand what it
is and how serious it is.

Bye,
Dav

[Bruce Long]

On Fri, Apr 8, 2011 at 10:28 AM, Davide Del Vento <davide.d...@gmail.com> wrote:

Folks,

I assume that the list of bugs on github is incomplete, right? I don't
understand bug #1 (yet) is it deal breaking? I wrote a comment to bug
#3. I also created labels, the idea is to label every bug with either:

It's incomplete. I'll work on making it as complete AFIK this weekend.

I think that bug #1 may have been fixed when I fixed something else. I'll check eventually, but it's not an important bug yet. (Something was getting done twice but done correctly so the only result is that eventually it would slow things down.)

 

workaround-available (probably won't get fixed now, since with a
different syntax you can get the same result, but keep it documented)
minor (we'll see if we'll fix it)
major (show stopper)
maybe others in between, if we think we need them

Cool.

 

And then with other labels to identity where the bug belong, e.g.
clip, ptest, slyp, proteus, etc.

I'm tempted to write a bug for the {...} problem so we don't have to
remember that's buried in bugs #3 and/or #4 (and then make those
"possible duplicates" of the first one). What do you think?

I hope that the exec bug is merely the {...} bug. That would be cool. I won't be able to check that for awhile. David, you did some experimenting with the {...} bug. Does the exec bug look like an instance of the same bug?

 

Let me know if you want me to look at any bug right now, e.g. the
range bug (I saw it mentioned in several places, including here:
http://infomage.com/newsandevents.html) but I don't understand what it
is and how serious it is.

The range bug is probably the most serious bug left. I need to do an analysis of it but haven't had time. When the range bug is done we should be able to parse/print and stream/struct.