<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in FormatUtil.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>cdc514e4 - [lldb] Update header guards to be consistent and compliant with LLVM (NFC)</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h#cdc514e4</link>
        <description>[lldb] Update header guards to be consistent and compliant with LLVM (NFC)LLDB has a few different styles of header guards and they&apos;re not veryconsistent because things get moved around or copy/pasted. This patchunifies the header guards across LLDB and converts everything to matchLLVM&apos;s style.Differential revision: https://reviews.llvm.org/D74743

            List of files:
            /llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h</description>
        <pubDate>Mon, 17 Feb 2020 23:57:45 +0000</pubDate>
        <dc:creator>Jonas Devlieghere &lt;jonas@devlieghere.com&gt;</dc:creator>
    </item>
<item>
        <title>2946cd70 - Update the file headers across all of the LLVM projects in the monorepo</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h#2946cd70</link>
        <description>Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we&apos;re moving the headerentirely to discuss the new license. We checked this carefully with theFoundation&apos;s lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636

            List of files:
            /llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h</description>
        <pubDate>Sat, 19 Jan 2019 08:50:56 +0000</pubDate>
        <dc:creator>Chandler Carruth &lt;chandlerc@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d211d1a5 - lldb-test: Improve newline handling</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h#d211d1a5</link>
        <description>lldb-test: Improve newline handlingSummary:Previously lldb-test&apos;s LinePrinter would output the indentation spaceseven on completely empty lines. This is not nice, as trailing spaces getflagged as errors in some tools/editors, and it prevents FileCheck&apos;sCHECK-EMPTY from working.Equally annoying was the fact that the LinePrinter did not terminateit&apos;s output with a newline (instead it would leave the unterminated hangingindent from the last NewLine() command), which meant that the shell promptfollowing the lldb-test command came out wrong.This fixes both issues by changing how newlines are handled. NewLine(),which was ending the previous line (&apos;\n&apos;) *and* begging the next line byprinting the indent, is now &quot;demoted&quot; to just printing literal &quot;\n&quot;.Instead, lines are now delimited via a helper Line object, which makessure the line is indented and terminated in an RAII fashion. The typicalusage would be:Printer.line() &lt;&lt; &quot;This text will be indented and terminated&quot;;If one needs to do more work than it will fit into a single statement,one can also assign the result of the line() function to a localvariable. The line will then be terminated when that object goes out ofscope.Reviewers: zturnerSubscribers: lldb-commitsDifferential Revision: https://reviews.llvm.org/D55597llvm-svn: 349269

            List of files:
            /llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h</description>
        <pubDate>Sat, 15 Dec 2018 13:49:25 +0000</pubDate>
        <dc:creator>Pavel Labath &lt;pavel@labath.sk&gt;</dc:creator>
    </item>
<item>
        <title>888a4282 - Add lldb-test.</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h#888a4282</link>
        <description>Add lldb-test.This is basically a proof-of-concept and starting point for having atesting-centric tool in LLDB.  I&apos;m sure this leaves a lot of room to bedesired, but this at least allows us to have something to build on.Right now there is only one command, the `module-sections` command, and Icreated this command not because it was particularly special, butbecause it addressed an immediate use case and was extremely simple.Run the tool as `lldb-test module-sections &lt;path-to-object&gt;`.Feel free to add testing related stuff to your heart&apos;s content afterthis goes in.  Implementing the commands themselves takes some work, butonce they&apos;re there they can be reused without writing any code andresult in very easy to use and maintain tests.Differential Revision: https://reviews.llvm.org/D40636llvm-svn: 319504

            List of files:
            /llvm-project-15.0.7/lldb/tools/lldb-test/FormatUtil.h</description>
        <pubDate>Fri, 01 Dec 2017 00:52:51 +0000</pubDate>
        <dc:creator>Zachary Turner &lt;zturner@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
