boostorg/preprocessor
1
0
Fork 1
mirror of https://github.com/boostorg/preprocessor.git synced 2025-07-19 07:22:07 +02:00
Code Issues Packages Projects Releases Wiki Activity

lib cleanup

Browse Source 
[SVN r15693]
This commit is contained in:
Paul Mensonides
2002-10-03 22:13:37 +00:00
parent ae584c68b2
commit 4bb690a819
263 changed files with 14965 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/terms/evaluated.html Normal file
View File

@ -0,0 +1,16 @@
<html>
<head>
<title>Evaluated Parameter</title>
<link rel="stylesheet" type="text/css" href="../styles.css">
</head>
<body>
<h4>Evaluated Parameter</h4>
<div>
An <i>evaluated parameter</i> is a numeric value that is evaluated by the library as a constant expression.&nbsp;
This means that the expression can include simple arithmetic, logical, and condition expressions.&nbsp;
It also means that the value of the parameter no longer depends on the source of the parameter.&nbsp;
In other words, if the value is dependent on some macro, it will no longer be dependent on that macro after it is evaluated.&nbsp;
This disables the lazy-evaluation that the preprocessor normallly uses.
</div>
</body>
</html>

14
doc/terms/named_external.html Normal file
View File

@ -0,0 +1,14 @@
<html>
<head>
<title>Named External Argument</title>
<link rel="stylesheet" type="text/css" href="../styles.css">
</head>
<body>
<h4>Named External Argument</h4>
<div>
A <i>named external argument</i> is an argument to a macro that is <i>included</i>.&nbsp;
There is no way to pass arguments to a file directly, so they must be passed to files in the form of macros with known names that are defined by the user.&nbsp;
Every time that the library uses this idiom, the file that is included automatically undefines the macro in order to better simulate <i>normal</i> parameters.
</div>
</body>
</html>