This allows Python or .gyb files to do "import gyb" and use the basic
components of the system. For example, we could create a Python
function to generate the boilerplate for a Mirror. That function could
use gyb.parseTemplate() to load an inline template and
gyb.executeTemplate() to generate the code. Then calls to that function
can be embedded in ${...} in a .gyb file.
Swift SVN r19490
Diagnostic output from compiling .swift files is now passed through the
line-directive tool so that errors point back at the original .gyb
files.
Swift SVN r15674
Literal text was being returned from the tokenizer with the regexp match
object for the /next/ token, if any. We need to know the beginning of
the text if we're going to generate #line markers.
Swift SVN r15341
This is fast enough to do all the time and will prevent problems like
the one noted as fixed below.
Also, fix a gyb self-test that had drifted out-of-date.
Swift SVN r14484
It was hard to decide on a replacement character for @, which is a
particularly bad choice for gyb ever since we started using it for
attributes in Swift, since attributes often start a line. Only
graphically-dense characters seem to look right. '%' has the
disadvantage of clashing with SIL, where it begins many lines, but we're
not using gyb to generate any SIL files today, so I optimized for the
common case.
Swift SVN r14483
For consistency with the vague idea that things that are only useful for
compiler developers should go in utils/, not tools/. Unless they need
build system support.
Swift SVN r9433
