Eli Schwartz 0a9048e554 compilers: don't use instance checks to determine properties ... In various situations we want to figure out what type of compiler we have, because we want to know stuff like "is it the pgi one", or "does it use msvc style". The compiler object has this property already, via an API specifically designed to communicate this info, but instead we performed isinstance checks on a compiler class. This is confusing and indirect, and has the side effect of requiring more imports everywhere. We should do away with it.		2022-09-19 15:18:59 -04:00
..
__init__.py	Moved backends to their own module.	2016-01-23 20:02:52 +02:00
backends.py	backends: limit maximum path of generated filenames	2022-09-11 14:51:03 -04:00
ninjabackend.py	compilers: don't use instance checks to determine properties	2022-09-19 15:18:59 -04:00
vs2010backend.py	vs: Fix CustomBuild contents.	2022-09-09 18:37:30 -04:00
vs2012backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
vs2013backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
vs2015backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
vs2017backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
vs2019backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
vs2022backend.py	treewide: various cleanups to move imports for mypy into typechecking blocks	2022-06-10 09:15:48 -04:00
xcodebackend.py	backend: always use the same code to compute the files in ExtractedObjects	2022-06-14 10:11:22 -07:00