===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
bornagain-1.16.0/.travis/linux/install.sh:1:docker build -t bornagain/wily -f `dirname $0`/Dockerfile .
bornagain-1.16.0/.travis/linux/install.sh-2-docker run -d --name dd -it bornagain/wily
##############################################
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-198-
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:199:#define getfpscr(x) asm volatile ("mffs %0" : "=f" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:200:#define setfpscr(x) asm volatile ("mtfsf 255,%0" : : "f" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-201-
##############################################
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-214-// x87 fpu
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:215:#define getx87cr(x) asm ("fnstcw %0" : "=m" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:216:#define setx87cr(x) asm ("fldcw %0" : "=m" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:217:#define getx87sr(x) asm ("fnstsw %0" : "=m" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-218-
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-219-// SIMD, gcc with Intel Core 2 Duo uses SSE2(4)
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:220:#define getmxcsr(x) asm ("stmxcsr %0" : "=m" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c:221:#define setmxcsr(x) asm ("ldmxcsr %0" : "=m" (x));
bornagain-1.16.0/Core/Tools/fp_exception_glibc_extension.c-222-
##############################################
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-991-\end{equation*}
bornagain-1.16.0/Doc/UserManual/Assemblies.tex:992:where $D(\alpha_0,\alpha_1) = D_0 + \kappa \left[ \Delta R(\alpha_0) + \Delta R(\alpha_1) \right]$, with $\Delta R(\alpha_i)$ the deviation of a size parameter of particle $i$ with respect to the mean over all particles sizes/shapes and $\kappa$ the coupling parameter.
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-993-
##############################################
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-1048-\end{align}
bornagain-1.16.0/Doc/UserManual/Assemblies.tex:1049:where $q_{\plll}$ is the component of the scattering beam in the plane of the interface ($\q=\k_i-\k_\sf$), $k_{i,z}$ and $k_{f,z}$ are the z-component of the incident and scattered beam, respectively. $R_i$, $R_f$ are the reflection coefficients in incidence and reflection. They are defined as\\ $R=\dfrac{k_z+\sqrt{n_s^2k_0^2-|k_{\plll}|^2}}{k_z-\sqrt{n_s^2 k_0^2-|k_{\plll}|^2}}$, where $n_s=1-\delta_s +i \beta_s$ is the refractive index of the substrate, $k_0$ is the wavelength in vacuum ($2\pi /\lambda$), $k_z$ and $k_{\plll}$ are the $z$-component and the in-plane component of $\k_\si$ or $\k_\sf$. \\
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-1050-
##############################################
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-1527-\end{center}
bornagain-1.16.0/Doc/UserManual/Assemblies.tex:1528:\caption{Schematics of the ideal 2D paracrystal. The gray-shaded areas mark the regions where the probability to find a node is larger that the width at half-maximum of the distribution. $L$ and $W$ are the mean inter-node distances along the two crystallographic axes. cl$_{(L,W),(x,y)}$ are the widths of the distribution of distance. The disorder is propagated as we add more nodes. Such a structure would be generated using \Code{InterferenceFunction2DParacrystal(L,W,90.*degrees,0,damp\_length)}, with \Code{pdf$_1$ = FTDistribution2DGauss(cl$_{L,x}$,cl$_{L,y}$)} and \Code{pdf$_2$ = FTDistribution2DGauss(cl$_{W,x}$,cl$_{W,y}$)}.}
bornagain-1.16.0/Doc/UserManual/Assemblies.tex-1529-\label{fig:2dparaschematic}
##############################################
bornagain-1.16.0/Doc/UserManual/Multilayers.tex-435-except for $l=0$,
bornagain-1.16.0/Doc/UserManual/Multilayers.tex:436:where the special definition of $z_0$ (\cref{Fdefz}) implies $d_0=0$.
bornagain-1.16.0/Doc/UserManual/Multilayers.tex-437-We consider the interface between layers $l$ and $l-1$,
##############################################
bornagain-1.16.0/ThirdParty/Fit/RootMinimizers/mathcore/Math/PdfFuncMathCore.h-298- \f[ \phi(\lambda) = \frac{1}{2 \pi i}\int_{c-i\infty}^{c+i\infty} e^{\lambda s + s \log{s}} ds\f]
bornagain-1.16.0/ThirdParty/Fit/RootMinimizers/mathcore/Math/PdfFuncMathCore.h:299: where \f$\lambda = (x-x_0)/\xi\f$. For a detailed description see
bornagain-1.16.0/ThirdParty/Fit/RootMinimizers/mathcore/Math/PdfFuncMathCore.h-300- K.S. Kölbig and B. Schorr, A program package for the Landau distribution,
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-12-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md:13:Suppose you put Google Test in directory `${GTEST_DIR}`. To build it,
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-14-create a library build target (or a project as called by Visual Studio
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-18-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md:19:with `${GTEST_DIR}/include` in the system header search path and `${GTEST_DIR}`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-20-in the normal header search path. Assuming a Linux-like system and gcc,
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-29-Next, you should compile your test source file with
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md:30:`${GTEST_DIR}/include` in the system header search path, and link it
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/README.md-31-with gtest and any other necessary libraries:
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md-1889-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md:1890:| `$ foo_test --gtest_repeat=1000` | Repeat foo\_test 1000 times and don't stop at failures. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md-1891-|:---------------------------------|:--------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md:1892:| `$ foo_test --gtest_repeat=-1` | A negative count means repeating forever. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md:1893:| `$ foo_test --gtest_repeat=1000 --gtest_break_on_failure` | Repeat foo\_test 1000 times, stopping at the first failure. This is especially useful when running under a debugger: when the testfails, it will drop into the debugger and you can then inspect variables and stacks. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md:1894:| `$ foo_test --gtest_repeat=1000 --gtest_filter=FooBar` | Repeat the tests whose name matches the filter 1000 times. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/AdvancedGuide.md-1895-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/FAQ.md-149-`Intermediate Directory` setting, change the value from
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/FAQ.md:150:`$(PlatformName)\$(ConfigurationName)` to
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/FAQ.md:151:`$(OutDir)\$(ProjectName)`. Click `OK` and then build the
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/FAQ.md-152-solution. When the build is complete, the 64-bit binaries will be in
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-48-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:49:The following Pump code (where meta keywords start with `$`, `[[` and `]]` are meta brackets, and `$$` starts a meta comment that ends with the line):
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-50-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-121-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:122:| `$var id = exp` | Defines a named constant value. `$id` is valid util the end of the current meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-123-|:----------------|:-----------------------------------------------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:124:| `$range id exp..exp` | Sets the range of an iteration variable, which can be reused in multiple loops later. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:125:| `$for id sep [[ code ]]` | Iteration. The range of `id` must have been defined earlier. `$id` is valid in `code`. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:126:| `$($)` | Generates a single `$` character. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:127:| `$id` | Value of the named constant or iteration variable. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:128:| `$(exp)` | Value of the expression. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:129:| `$if exp [[ code ]] else_branch` | Conditional. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-130-| `[[ code ]]` | Meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-131-| `cpp_code` | Raw C++ code. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:132:| `$$ comment` | Meta comment. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-133-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-134-**Note:** To give the user some freedom in formatting the Pump source
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:135:code, Pump ignores a new-line character if it's right after `$for foo`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-136-or next to `[[` or `]]`. Without this rule you'll often be forced to write
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-175-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md:176: * If a meta variable is followed by a letter or digit, you can separate them using `[[]]`, which inserts an empty string. For example `Foo$j[[]]Helper` generate `Foo1Helper` when `j` is 1.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/PumpManual.md-177- * To avoid extra-long Pump source lines, you can break a line anywhere you want by inserting `[[]]` followed by a new line. Since any new-line character next to `[[` or `]]` is ignored, the generated code won't contain this new line.
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md-1805-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md:1806:| `$ foo_test --gtest_repeat=1000` | Repeat foo\_test 1000 times and don't stop at failures. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md-1807-|:---------------------------------|:--------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md:1808:| `$ foo_test --gtest_repeat=-1` | A negative count means repeating forever. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md:1809:| `$ foo_test --gtest_repeat=1000 --gtest_break_on_failure` | Repeat foo\_test 1000 times, stopping at the first failure. This is especially useful when running under a debugger: when the testfails, it will drop into the debugger and you can then inspect variables and stacks. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md:1810:| `$ foo_test --gtest_repeat=1000 --gtest_filter=FooBar` | Repeat the tests whose name matches the filter 1000 times. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_AdvancedGuide.md-1811-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_FAQ.md-55-`Intermediate Directory` setting, change the value from
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_FAQ.md:56:`$(PlatformName)\$(ConfigurationName)` to
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_FAQ.md:57:`$(OutDir)\$(ProjectName)`. Click `OK` and then build the
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_FAQ.md-58-solution. When the build is complete, the 64-bit binaries will be in
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-48-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:49:The following Pump code (where meta keywords start with `$`, `[[` and `]]` are meta brackets, and `$$` starts a meta comment that ends with the line):
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-50-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-121-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:122:| `$var id = exp` | Defines a named constant value. `$id` is valid util the end of the current meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-123-|:----------------|:-----------------------------------------------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-124-| $range id exp..exp | Sets the range of an iteration variable, which can be reused in multiple loops later. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:125:| $for id sep [[code ](.md)] | Iteration. The range of `id` must have been defined earlier. `$id` is valid in `code`. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:126:| `$($)` | Generates a single `$` character. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:127:| `$id` | Value of the named constant or iteration variable. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:128:| `$(exp)` | Value of the expression. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:129:| `$if exp [[ code ]] else_branch` | Conditional. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-130-| `[[ code ]]` | Meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-131-| `cpp_code` | Raw C++ code. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:132:| `$$ comment` | Meta comment. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-133-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-134-**Note:** To give the user some freedom in formatting the Pump source
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:135:code, Pump ignores a new-line character if it's right after `$for foo`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-136-or next to `[[` or `]]`. Without this rule you'll often be forced to write
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-175-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md:176: * If a meta variable is followed by a letter or digit, you can separate them using `[[]]`, which inserts an empty string. For example `Foo$j[[]]Helper` generate `Foo1Helper` when `j` is 1.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_5_PumpManual.md-177- * To avoid extra-long Pump source lines, you can break a line anywhere you want by inserting `[[]]` followed by a new line. Since any new-line character next to `[[` or `]]` is ignored, the generated code won't contain this new line.
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md-1887-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md:1888:| `$ foo_test --gtest_repeat=1000` | Repeat foo\_test 1000 times and don't stop at failures. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md-1889-|:---------------------------------|:--------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md:1890:| `$ foo_test --gtest_repeat=-1` | A negative count means repeating forever. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md:1891:| `$ foo_test --gtest_repeat=1000 --gtest_break_on_failure` | Repeat foo\_test 1000 times, stopping at the first failure. This is especially useful when running under a debugger: when the testfails, it will drop into the debugger and you can then inspect variables and stacks. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md:1892:| `$ foo_test --gtest_repeat=1000 --gtest_filter=FooBar` | Repeat the tests whose name matches the filter 1000 times. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_AdvancedGuide.md-1893-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_FAQ.md-149-`Intermediate Directory` setting, change the value from
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_FAQ.md:150:`$(PlatformName)\$(ConfigurationName)` to
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_FAQ.md:151:`$(OutDir)\$(ProjectName)`. Click `OK` and then build the
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_FAQ.md-152-solution. When the build is complete, the 64-bit binaries will be in
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-48-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:49:The following Pump code (where meta keywords start with `$`, `[[` and `]]` are meta brackets, and `$$` starts a meta comment that ends with the line):
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-50-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-121-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:122:| `$var id = exp` | Defines a named constant value. `$id` is valid util the end of the current meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-123-|:----------------|:-----------------------------------------------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:124:| `$range id exp..exp` | Sets the range of an iteration variable, which can be reused in multiple loops later. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:125:| `$for id sep [[ code ]]` | Iteration. The range of `id` must have been defined earlier. `$id` is valid in `code`. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:126:| `$($)` | Generates a single `$` character. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:127:| `$id` | Value of the named constant or iteration variable. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:128:| `$(exp)` | Value of the expression. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:129:| `$if exp [[ code ]] else_branch` | Conditional. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-130-| `[[ code ]]` | Meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-131-| `cpp_code` | Raw C++ code. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:132:| `$$ comment` | Meta comment. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-133-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-134-**Note:** To give the user some freedom in formatting the Pump source
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:135:code, Pump ignores a new-line character if it's right after `$for foo`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-136-or next to `[[` or `]]`. Without this rule you'll often be forced to write
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-175-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md:176: * If a meta variable is followed by a letter or digit, you can separate them using `[[]]`, which inserts an empty string. For example `Foo$j[[]]Helper` generate `Foo1Helper` when `j` is 1.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_6_PumpManual.md-177- * To avoid extra-long Pump source lines, you can break a line anywhere you want by inserting `[[]]` followed by a new line. Since any new-line character next to `[[` or `]]` is ignored, the generated code won't contain this new line.
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md-1888-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md:1889:| `$ foo_test --gtest_repeat=1000` | Repeat foo\_test 1000 times and don't stop at failures. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md-1890-|:---------------------------------|:--------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md:1891:| `$ foo_test --gtest_repeat=-1` | A negative count means repeating forever. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md:1892:| `$ foo_test --gtest_repeat=1000 --gtest_break_on_failure` | Repeat foo\_test 1000 times, stopping at the first failure. This is especially useful when running under a debugger: when the testfails, it will drop into the debugger and you can then inspect variables and stacks. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md:1893:| `$ foo_test --gtest_repeat=1000 --gtest_filter=FooBar` | Repeat the tests whose name matches the filter 1000 times. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_AdvancedGuide.md-1894-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_FAQ.md-149-`Intermediate Directory` setting, change the value from
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_FAQ.md:150:`$(PlatformName)\$(ConfigurationName)` to
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_FAQ.md:151:`$(OutDir)\$(ProjectName)`. Click `OK` and then build the
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_FAQ.md-152-solution. When the build is complete, the 64-bit binaries will be in
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-48-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:49:The following Pump code (where meta keywords start with `$`, `[[` and `]]` are meta brackets, and `$$` starts a meta comment that ends with the line):
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-50-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-121-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:122:| `$var id = exp` | Defines a named constant value. `$id` is valid util the end of the current meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-123-|:----------------|:-----------------------------------------------------------------------------------------------|
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:124:| `$range id exp..exp` | Sets the range of an iteration variable, which can be reused in multiple loops later. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:125:| `$for id sep [[ code ]]` | Iteration. The range of `id` must have been defined earlier. `$id` is valid in `code`. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:126:| `$($)` | Generates a single `$` character. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:127:| `$id` | Value of the named constant or iteration variable. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:128:| `$(exp)` | Value of the expression. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:129:| `$if exp [[ code ]] else_branch` | Conditional. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-130-| `[[ code ]]` | Meta lexical block. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-131-| `cpp_code` | Raw C++ code. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:132:| `$$ comment` | Meta comment. |
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-133-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-134-**Note:** To give the user some freedom in formatting the Pump source
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:135:code, Pump ignores a new-line character if it's right after `$for foo`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-136-or next to `[[` or `]]`. Without this rule you'll often be forced to write
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-175-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md:176: * If a meta variable is followed by a letter or digit, you can separate them using `[[]]`, which inserts an empty string. For example `Foo$j[[]]Helper` generate `Foo1Helper` when `j` is 1.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/docs/V1_7_PumpManual.md-177- * To avoid extra-long Pump source lines, you can break a line anywhere you want by inserting `[[]]` followed by a new line. Since any new-line character next to `[[` or `]]` is ignored, the generated code won't contain this new line.
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4-58- AS_IF([test "x${HAVE_GTEST}" = "xyes"],
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4:59: [GTEST_CPPFLAGS=`${GTEST_CONFIG} --cppflags`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4:60: GTEST_CXXFLAGS=`${GTEST_CONFIG} --cxxflags`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4:61: GTEST_LDFLAGS=`${GTEST_CONFIG} --ldflags`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4:62: GTEST_LIBS=`${GTEST_CONFIG} --libs`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4:63: GTEST_VERSION=`${GTEST_CONFIG} --version`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/m4/gtest.m4-64- AC_DEFINE([HAVE_GTEST],[1],[Defined when Google Test is available.])],
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in-205-bindir="@bindir@"
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in:206:this_relative_bindir=`dirname $0`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in:207:this_bindir=`cd ${this_relative_bindir}; pwd -P`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in-208-if test "${this_bindir}" = "${this_bindir%${bindir}}"; then
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in-210- # assume that we are in a build tree.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in:211: build_dir=`dirname ${this_bindir}`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in:212: src_dir=`cd ${this_bindir}; cd @top_srcdir@; pwd -P`
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/scripts/gtest-config.in-213-
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-3105- } else {
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc:3106: printf(", where %s = %s\n", kTypeParamLabel, test_case.type_param());
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-3107- }
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-4883- // the output easy to parse by a program.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc:4884: PrintOnOneLine(test_case->type_param(), kMaxParamLength);
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-4885- }
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-4892- // output easy to parse by a program.
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc:4893: PrintOnOneLine(test_info->value_param(), kMaxParamLength);
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/src/gtest.cc-4894- }
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc-806-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc:807: EXPECT_EQ(::testing::PrintToString(GetParam()), test_info->value_param());
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc-808-}
##############################################
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc-980-
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc:981: EXPECT_EQ(::testing::PrintToString(GetParam()), test_info->value_param());
bornagain-1.16.0/ThirdParty/common/gtest/gtest-1.8.0/test/gtest-param-test_test.cc-982-}
##############################################
bornagain-1.16.0/cmake/bornagain/modules/NSIS.template.in-355- Push "$0;"
bornagain-1.16.0/cmake/bornagain/modules/NSIS.template.in:356: Call un.StrStr ; Find `$0;` in $1
bornagain-1.16.0/cmake/bornagain/modules/NSIS.template.in-357- Pop $2 ; pos of our dir
##############################################
bornagain-1.16.0/cmake/bornagain/modules/SearchInstalledSoftware.cmake-81- find_package(SWIG 3.0 REQUIRED)
bornagain-1.16.0/cmake/bornagain/modules/SearchInstalledSoftware.cmake:82: include(${SWIG_USE_FILE})
bornagain-1.16.0/cmake/bornagain/modules/SearchInstalledSoftware.cmake-83- message(STATUS "Found SWIG version ${SWIG_VERSION} at ${SWIG_EXECUTABLE} with flags '${SWIG_FLAGS}'; CMake definitions in ${SWIG_USE_FILE}")
##############################################
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in-21-if ("$ARGS" != "") then
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in:22: set thisbornagain="`dirname ${ARGS[2]}`"
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in-23-else
##############################################
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in-51-
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in:52:setenv BORNAGAINSYS "`(cd ${thisbornagain}/..;pwd)`"
bornagain-1.16.0/cmake/bornagain/scripts/thisbornagain.csh.in-53-
##############################################
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake-34-#
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake:35:# This script expects to find libraries at ``$GSL_ROOT_DIR/lib`` and the GSL
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake:36:# headers at ``$GSL_ROOT_DIR/include/gsl``. The library directory may
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake-37-# optionally provide Release and Debug folders. For Unix-like systems, this
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake:38:# script will use ``$GSL_ROOT_DIR/bin/gsl-config`` (if found) to aid in the
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake-39-# discovery GSL.
##############################################
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake-68-# Include these modules to handle the QUIETLY and REQUIRED arguments.
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake:69:#include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake) # original
bornagain-1.16.0/cmake/generic/modules/FindGSL.cmake-70-include(FindPackageHandleStandardArgs) # patched JWu 4/16
##############################################
bornagain-1.16.0/.pc/0002-use-the-system-eigen3.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake-87- find_package(SWIG 3.0 REQUIRED)
bornagain-1.16.0/.pc/0002-use-the-system-eigen3.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake:88: include(${SWIG_USE_FILE})
bornagain-1.16.0/.pc/0002-use-the-system-eigen3.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake-89- message(STATUS "Found SWIG version ${SWIG_VERSION} at ${SWIG_EXECUTABLE} with flags '${SWIG_FLAGS}'; CMake definitions in ${SWIG_USE_FILE}")
##############################################
bornagain-1.16.0/.pc/0005-Add-3.8-to-list-of-supported-python-versions.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake-81- find_package(SWIG 3.0 REQUIRED)
bornagain-1.16.0/.pc/0005-Add-3.8-to-list-of-supported-python-versions.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake:82: include(${SWIG_USE_FILE})
bornagain-1.16.0/.pc/0005-Add-3.8-to-list-of-supported-python-versions.patch/cmake/bornagain/modules/SearchInstalledSoftware.cmake-83- message(STATUS "Found SWIG version ${SWIG_VERSION} at ${SWIG_EXECUTABLE} with flags '${SWIG_FLAGS}'; CMake definitions in ${SWIG_USE_FILE}")