Use #if not defined with OR boolean logic in preprocessor directives
I am currently using Linux CentOS and programming in FORTRAN 90 using Portland 7.1 compiler.
I am able to set in the preprocessor directives a flag called TEST. when I go to use logic in my code i can write
Furthermore, if I want to negate the logic I can type:
Now, if I want to add some boolean logic like AND, OR etc. I have to use slightly different syntax as follows:
This allows me to say if the Flag "TEST" or the flag "NEWTEST" is defined then do something. What I cannot seem to find is how to negate the logic such that it says: if the Flag "TEST" is NOT defined OR the flag NEWTEST is NOT defined...
The syntax I have tried to come up with does not appear to work. I am looking for something similar to the following:
Any ideas??
Last edited by prodigious8; 03-15-2016 at 01:57 PM..
Reason: OR will not be valid for the logic I want
Is there a general rule I can apply when examining/editing ipfw entries?
Also, does each new entry have to have a unique rule number?
And, I think I can write a script to block code red infected machines (though I'm not sure it would do more than slim down my web server error message log),... (0 Replies)
Hello,
Is there anyway to prevent users from modifying limits imposed by php.ini configuration in a phpSuExec configured PHP installation??
For example in server with PHP running in a module, I use php_admin_* directives:
php_admin_value memory_limit 40M
And users can't modify them... (0 Replies)
Hi,
Anyone please explain the functionality of ## in c.
I didn't get the following preprocessor directives,
# define LL(x) x ## LL
# define LL(x) x ## i64
Thanks,
Naga:cool: (1 Reply)
I have four files a,b,c,d which need to contain certain in the sequence a, b, c ,d , each file command which needs to be executed,
what i m in need is that to executed file and cmd in the defined order and if any of the command FAIL or throw ERROR, it script shud come out... (3 Replies)
Say I have a list of enumerations I wish to use to select a variable at compile-time:
enum pins
{
PIN_A=1,
PIN_B=7,
PIN_C=6,
}
int VAR1, VAR2, VAR3, VAR4, VAR5, VAR6, VAR7;
#define PIN_TO_VAR(NUM) VAR ## NUM
int main(void)
{
PIN_TO_VAR(PIN_A)=32;... (2 Replies)
Hi,
Just wondering if it is possible to trim the file path output by __FILE__ preprocessor in my debugging line.
Let's say my main.cpp file is found in C:\User\MyName\SystemA\Mod1\SubMod2\Test\main.cpp
for __FILE__, I just want the filename - main.cpp to be printed, instead of the entire... (2 Replies)
Hi,
I was reviewing a shell script and I found this line:
yum -y update >> >(/usr/bin/tee /var/log/file)
I have tried removing the >> directive and all that will occur is that the file will be created--nothing gets put in the file. If I put back the >> directive it works. If I remove the... (3 Replies)
Discussion started by: mojoman
3 Replies
LEARN ABOUT CENTOS
rake
RAKE(1) Ruby Programmers Reference Guide RAKE(1)NAME
rake -- Ruby Make
SYNOPSIS
rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE] [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE]
[-r MODULE] [--rules] [variable=value] target ...
DESCRIPTION
Rake is a simple ruby(1) build program with capabilities similar to the regular make(1) command.
Rake has the following features:
o Rakefiles (Rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax
to worry about (is that a tab or a space?).
o Users can specify tasks with prerequisites.
o Rake supports rule patterns to synthesize implicit tasks.
o Flexible FileLists that act like arrays but know about manipulating file names and paths.
o A library of prepackaged tasks to make building rakefiles easier.
OPTIONS --version Display the program version.
-C
--classic-namespace
Put Task and FileTask in the top level namespace
-D [PATTERN]
--describe [PATTERN]
Describe the tasks (matching optional PATTERN), then exit.
-E CODE
--execute-continue CODE
Execute some Ruby code, then continue with normal task processing.
-G
--no-system
--nosystem Use standard project Rakefile search paths, ignore system wide rakefiles.
-I LIBDIR
--libdir LIBDIR Include LIBDIR in the search path for required modules.
-N
--no-search
--nosearch Do not search parent directories for the Rakefile.
-P
--prereqs Display the tasks and dependencies, then exit.
-R RAKELIBDIR
--rakelib RAKELIBDIR
--rakelibdir RAKELIBDIR
Auto-import any .rake files in RAKELIBDIR. (default is rakelib )
-T [PATTERN]
--tasks [PATTERN] Display the tasks (matching optional PATTERN) with descriptions, then exit.
-e CODE
--execute CODE Execute some Ruby code and exit.
-f FILE
--rakefile FILE Use FILE as the rakefile.
-h
--help Prints a summary of options.
-g
--system Using system wide (global) rakefiles (usually ~/.rake/*.rake ).
-n
--dry-run Do a dry run without executing actions.
-p CODE
--execute-print CODE
Execute some Ruby code, print the result, then exit.
-q
--quiet Do not log messages to standard output.
-r MODULE
--require MODULE Require MODULE before executing rakefile.
-s
--silent Like --quiet, but also suppresses the 'in directory' announcement.
-t
--trace Turn on invoke/execute tracing, enable full backtrace.
-v
--verbose Log message to standard output (default).
--rules Trace the rules resolution.
SEE ALSO ruby(1)make(1)
http://rake.rubyforge.org/
REPORTING BUGS
Bugs, features requests and other issues can be logged at <http://onestepback.org/redmine/projects/show/rake>.
You will need an account to before you can post issues. Register at <http://onestepback.org/redmine/account/register>. Or you can send an
email to the author.
AUTHOR
Rake is written by Jim Weirich <jim@weirichhouse.org>
UNIX November 7, 2012 UNIX