On Fri, 07 Jan 2005 16:18:11 -0500, Kurt B. Kaiser <[EMAIL PROTECTED]> wrote: > Looks like it's done. I tagged ast-branch when I finished: > > merged_from_MAIN_07JAN05 > > Right now I'm trying to get Python-ast.c to compile. It wasn't > modified by the merge, so there's some other issue.
I'm getting a compilation failure in symtable.c: gcc -pthread -c -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I. -I../Include -DPy_BUILD_CORE -o Python/symtable.o ../Python/symtable.c ../Python/symtable.c: In function `symtable_new': ../Python/symtable.c:193: structure has no member named `st_tmpname' Do you see that? There is this one ugly corner of Python-ast.c. There's a routine that expects to take a pointer to a node, but instead gets passed an int. The generated code is bogus, and I haven't decided if it needs to be worried about. You need to manually edit the generated code to add a cast. > > And if I haven't already said thanks, then, thanks for doing it! > > You're welcome! I volunteer to keep ast-branch synch'd, how often > do you want to do it? I don't think we'll need to merge again. This last merge got all the language changes that were made for 2.4. Since we've agreed to a moratorium on more compiler/bytecode changes, we shouldn't need to merge from the head again. Jeremy _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
