rif <[EMAIL PROTECTED]> writes: > I'm happy to provide more code. I'm just not sure of the best way to > go about it. > > If I have to provide enough code so that the function compiles, that's > a few hundred lines, because vmap is a "little language"; also, I > can't really expect anyone else to go through hundreds of lines of my > code.
>From "How to Report Bugs Effectively" (http://www.chiark.greenend.org.uk/~sgtatham/bugs.html): * If you have to report a bug to a programmer who can't be present in * person, the aim of the exercise is to enable them to reproduce the * problem. You want the programmer to run their own copy of the program, * do the same things to it, and make it fail in the same way. When they * can see the problem happening in front of their eyes, then they can * deal with it. So just post the source code. If you can simplify it--it is probably a good thing. > Alternately, I could macroexpand all the code, and post a > macroexpanded version (with-gensyms somehow replaced). Would this be > useful? If you report a compiler failure--yes, but for disoptimization I'd say that source code is more interesting. > Of course, I could also post assembly or compiler traces if people > want. If you think that the problem is with your machine or you have a broken compiler version... -- Regards, Alexey Dejneka "Alas, the spheres of truth are less transparent than those of illusion." -- L.E.J. Brouwer
