I'm not one to comment on the microsoft "way". I have noticed a perverse desire to try to do things exactly backwards or different (read incompatible) with linux/unix standard practices. Thus we have things like spaces in the middle of file names and backslash as a directory delimiter instead of forward slash etc. In all fairness there is also an option to dump the defines to the standard output, which is actually less useful in my case.
My next question is how do I file this as a bug report? It seems I need an account on bug tracker, which gives me the cryptic instructions send e-mail to Robert Bradshaw (e-mail not provided) and to use some sort of automated password generator (htpasswd) which I've never used and probably doesn't exist in windows. Moreover I'm disinclined to dual boot into linux right now. -Matt On 2:59 PM, Dag Sverre Seljebotn wrote: > Matthew Bromberg wrote: > >> The way to coerce MS Visual Studio to show the includes is apparently >> with the /P option, which puts them in the source file. (So save a >> copy of the source if you need it). >> > That's hilarious! I wonder how somebody would even come up with behaviour > like this. > > Dag Sverre > > > _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
