Use JSON code blocks for compilation databases

Pennycook · Pennycook · commit 123d24efd632 · 2024-03-22T11:37:49.000-07:00
Signed-off-by: John Pennycook &lt;john.pennycook@intel.com&gt;
diff --git a/docs/source/compilation-databases.rst b/docs/source/compilation-databases.rst
@@ -68,7 +68,9 @@ to actually run :code:`make`.
     executed, allowing us to generate compilation databases without also
     building the application. Other tools (like Bear) may require a build.
 
-In this case, it contains::
+In this case, it contains:
+
+.. code :: json
 
     [
     {
@@ -102,7 +104,9 @@ compilation database for the GPU.
 
 As expected, we can see that the compilation database refers to ``gpu.cpp``
 instead of ``cpu.cpp``, and that the ``GPU_OFFLOAD`` macro is defined as part
-of each compilation command::
+of each compilation command:
+
+.. code :: json
 
     [
     {

Original file line number	Diff line number	Diff line change
@@ -68,7 +68,9 @@ to actually run :code:`make`.
`68`	`68`	`executed, allowing us to generate compilation databases without also`
`69`	`69`	`building the application. Other tools (like Bear) may require a build.`
`70`	`70`
`71`		`-In this case, it contains::`
	`71`	`+In this case, it contains:`
	`72`	`+`
	`73`	`+.. code :: json`
`72`	`74`
`73`	`75`	`[`
`74`	`76`	`{`
`@@ -102,7 +104,9 @@ compilation database for the GPU.`
`102`	`104`
`103`	`105`	As expected, we can see that the compilation database refers to ``gpu.cpp``
`104`	`106`	instead of ``cpu.cpp``, and that the ``GPU_OFFLOAD`` macro is defined as part
`105`		`-of each compilation command::`
	`107`	`+of each compilation command:`
	`108`	`+`
	`109`	`+.. code :: json`
`106`	`110`
`107`	`111`	`[`
`108`	`112`	`{`