Putting files of interest in different directories is also confusing. I, personally, prefer the .c(pp) files co-existing with the .pyx ones. I think it's pretty standard to have a single source tree have mixed source and compiler output during development--this goes back to the "make" vs "make install" discussion on the other thread.
On Sat, Jul 5, 2014 at 10:02 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > Not all C/C++ sources are auto-generated from Cython files. Some extension > modules in Sage use hand-written C/C++ source as well. If we litter the > cythonize output into the source tree (and cross our fingers that there is > no name collision with a hand-written C/C++ file) then it is potentially > even more confusing. > > There is of course more than one way of doing things, but IMHO if you are > debugging on the C level then you already have to come to terms that the > source/object/shared libraries live in different directories. It doesn't > strike me as a particular burden to look up the location of the intermediate > C sources. It is also explictly named on the gcc command line that we print > on the screen. > > > > > On Saturday, July 5, 2014 12:01:20 PM UTC-4, Ralf Stephan wrote: >> >> I just had a gotcha: previously when debugging a traceback in a cythonized >> file I took the line number in the trace, loaded the cpp file *from the same >> directory as the pyx file, and then looked at the resp. line in the pyx >> file---which was quick because both files are in the same directory. Now >> today I noticed my expression.cpp was not synced to expression.pyx and I >> could even delete the cpp without doing obvious harm. >> >> My questions: Is it necessary that current cpp files now live in >> build/cythonized/sage/ ? (it makes a cumbersome task of debugging even more >> cumbersome because the source tree has now to be climbed twice). Secondly if >> yes then why keep stale cpp files in src/sage? >> >> I'm certainly missing something here so please give me a hint. Regards, > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
