bearophile Wrote: > One solution is to "disable" some of the more error-prone syntax allowed in > C, turning it into a compilation error. For example I have seen newbies write > bugs caused by leaving & where a && was necessary. In such case just adopting > "and" and making "&&" a syntax error solves the problem and doesn't lead to > bugs when you convert C code to D (you just use a search&replace, replacing > && with and on the code).
Why do you want to turn D into Python? You already has one. Just write in python, migrate others to it and be done with C family.
