Re: [Chicken-users] obscure error message after refactoring
* Alan Post alanp...@sunflowerriver.org [110120 14:59]: I've been looking over diffs trying to see if I've introduced a subtle scope or syntax error somewhere, but I'm not having much luck. What do I do with an error message like the one above? It isn't obvious to me where I need to look to fix the problem. First of all try to increase the call-chain size with -:aN where N is the number of entries. Then it also might be that the error occurs after your stuff has been expanded by syntax. So have a look at the continuation of all this code. It may give some hints. I hope you can identify the culprit soon. Good luck hunting, Christian ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] obscure error message after refactoring
From: Alan Post alanp...@sunflowerriver.org Subject: [Chicken-users] obscure error message after refactoring Date: Thu, 20 Jan 2011 06:58:27 -0700 I don't have an explicit call to caddr anywhere in my code, and I believe the following line: syntax (##core#set! genturfahi-version trunk) Refers to the last line in the last file of my library. I've been looking over diffs trying to see if I've introduced a subtle scope or syntax error somewhere, but I'm not having much luck. What do I do with an error message like the one above? It isn't obvious to me where I need to look to fix the problem. This is an expansion error in a macro, or it's an internal compiler error. The code runs correctly when interpreted? cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] obscure error message after refactoring
On Thu, Jan 20, 2011 at 09:09:25AM -0500, Felix wrote: From: Alan Post alanp...@sunflowerriver.org Subject: [Chicken-users] obscure error message after refactoring Date: Thu, 20 Jan 2011 06:58:27 -0700 I don't have an explicit call to caddr anywhere in my code, and I believe the following line: syntax (##core#set! genturfahi-version trunk) Refers to the last line in the last file of my library. I've been looking over diffs trying to see if I've introduced a subtle scope or syntax error somewhere, but I'm not having much luck. What do I do with an error message like the one above? It isn't obvious to me where I need to look to fix the problem. This is an expansion error in a macro, or it's an internal compiler error. The code runs correctly when interpreted? The code runs differently when interpreted! It isn't currently matching any of my .peg files, but it does run to completion. I keep in my tests/ directory both .peg and .scm versions of my parsers. Normally, I use the .scm versions of my parsers to pinpoint precise problems in the code, as a failure to compile a .peg file is really just there's a problem somewhere. I haven't tried yet running my tests from the interpreter to see exactly what is not working like I expect. I did, for this change, include the matchable egg. I took some extra time checking to make sure I was using it correctly, though the error could still be in how I'm using that API. I believe it is the only difference in macro-using code I've changed. It's a fair hint anyway. -Alan -- .i ko djuno fi le do sevzi ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] obscure error message after refactoring
On Thu, Jan 20, 2011 at 03:08:53PM +0100, Christian Kellermann wrote: * Alan Post alanp...@sunflowerriver.org [110120 14:59]: I've been looking over diffs trying to see if I've introduced a subtle scope or syntax error somewhere, but I'm not having much luck. What do I do with an error message like the one above? It isn't obvious to me where I need to look to fix the problem. First of all try to increase the call-chain size with -:aN where N is the number of entries. Then it also might be that the error occurs after your stuff has been expanded by syntax. So have a look at the continuation of all this code. It may give some hints. I hope you can identify the culprit soon. increasing the call chain size doesn't affect the output, it seems. Can you explain what you mean by look at the continuation of all this code? I don't understand yet. -Alan -- .i ko djuno fi le do sevzi ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] obscure error message after refactoring
* Alan Post alanp...@sunflowerriver.org [110120 15:28]: increasing the call chain size doesn't affect the output, it seems. Can you explain what you mean by look at the continuation of all this code? I don't understand yet. I am refering to the location where the code shown in the call-chain is expanded. It might also be a macro that causes an error during expansion though. ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users