Sponsored Content
The Lounge What is on Your Mind? What technology you can't live without for a week? Post 302803169 by wisecracker on Monday 6th of May 2013 05:31:07 AM
Old 05-06-2013
None of the above...

The car...
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to identify week-1 and week-2

Hello Friends I have three dirs 1. /home/main-bkup 2. /home/bkup-week1 3. /home/bkup-week2 Now we copy backups in 1 initially, then on 1st week we copy few content of 1 into 2 and then run some scripts on that. Then in 2nd week we keep 2 untouched and do the same thing in 3. So I... (1 Reply)
Discussion started by: csaha
1 Replies

2. What is on Your Mind?

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates

Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates" The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
NYPATCHY(1)						      General Commands Manual						       NYPATCHY(1)

NAME
nypatchy - tool to work with specialized-format patches SYNOPSIS
nypatchy pam fort cradle print cc as data [ fort2 cc2 as2 data2 ] DESCRIPTION
nypatchy is a tool for working with Patchy Master Files (PAM files). A PAM file is an ordinary text file (generally with a three-letter extension of ".car") that holds source code interleaved with special pre-processing instructions for nypatchy. The source code may be in C, FORTRAN, assembly language, or a combination of these. The pre-processing instructions allow one to maintain separate optional patches independently, for instance in the case of architecture-specific code. Details of the pre-processing commands used by nypatchy are beyond the scope of this man page; the reader should refer to the full manual available from CERN. Telling nypatchy which set of patches to use may be done on standard input or via a so-called cradle file. Typically the cradle file will contain one or more +USE statements as well as +EXE and +QUIT, for instance in the case of the isajet Monte Carlo generator: +USE,*ISAJET +EXE +PAM +QUIT USAGE
In the command line shown above, pam is the PAM file, if any. fort is the name of the primary output source code file, if any. cradle is the name of the cradle file, if any (default is standard input, for instance a here-doc). print is the name of the file to receive printed output (the default is standard output). cc, as, data are the names of the source code output files for data types CC, AS, DATA. The remaining parameters are the source code output files to receive diverted material for respective data types FORT, CC, AS, DATA. Parameters may be omitted by substituting a dash - for them. Trailing parameters may be cut short by giving "." or ".go"; the latter com- mences execution immediately rather than starting the nypatchy interactive prompt. nypatchy will return to the shell a code of 0 if successful, 1 if there is a warning, and 2 if an error occurs. Since the program stops creating output, but continues to run (in order to check for further errors) if an error occurs, the user should be sure to test the error code $? after any nypatchy run. EXAMPLES
nypatchy -- xyz .go reads the cradle (instructions) from file xyz.cra, which must list all other files to be used. nypatchy .go << EOF <cradle> EOF has the cradle given as a here-document. nypatchy zebra.car zebra.fca zebra.cra zebra.lis .go reads the PAM file zebra.car, outputting the resulting source code to zebra.fca, taking the cradle from zebra.cra, with printing done to zebra.lis. SEE ALSO
fcasplit(1), nycheck(1), nydiff(1), nyindex(1), nylist(1), nymerge(1), nyshell(1), nysynopt(1), nytidy(1), yexpand(1) The reference manual for the Nypatchy suite of programs is available in compressed PostScript format at the following URL: http://wwwasdoc.web.cern.ch/wwwasdoc/psdir/p5refman.ps.gz Running the command "nypatchy help .no" also gives some brief help on usage. AUTHOR
This manual page was written by Kevin McCarty <kmccarty@debian.org> for the Debian GNU/Linux system (but may be used by others). It is licensed under the GNU General Public License, version 2 or later (at your choice). COPYRIGHT
Copyright (C) Kevin B. McCarty, 2008. Mar 12, 2008 NYPATCHY(1)
All times are GMT -4. The time now is 09:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy