Looking for guidance (comments) on a piece of code
Hello -- I am trying to learn to do a little sed and awk scripting to search for text and numbers in text files (text processing/manipulation). My professor gave me a piece of uncommented code and I am very unfamiliar w/ the language. Can someone help me with comments so I can understand what is happening in each line? I have cygwin running to run scripts.
thanks
Code:
BEGIN {ifreq=0; iint=0; ithresh=0.5; maxint=0.0}
/Wavenum|Frequencies/ {
for (i=3; i<=NF; i++) {
if ($i<freqs[ifreq-1] && ifreq>0) exit;
freqs[ifreq]=$i;
ifreq++;
}
}
/Inten/ { for (i=4; i<=NF; i++) {
ints[iint]=$i;
if (ints[iint]>maxint) maxint=ints[iint];
iint++;
}
}
END {
if (ifreq!=iint) {
print "Error: no. of Freqs doesn't match no. of ints.";
print "No. freqs = " ifreq " No. ints = " iint;
exit;
}
delta=0.001;
for (i=0; i<ifreq; i++) {
iscale=ints[i]/maxint;
print freqs[i], ints[i], iscale;
}
}
Moderator's Comments:
please use code tags
Last edited by jim mcnamara; 05-24-2012 at 12:11 AM..
use "getopts" to get params from command. Need replace black with a specified string like "%20
DEFAULT_DELIM＝％20
...
while getopts dek:f:t:vh OPTION
do
case $OPTION in
t)
DELIM=`tvar=/'"$OPTARG"'/ svar="$DEFAULT_DELIM" awk 'BEGIN{T=ENVIRON;S=ENVIRON; while(index(T,S)!=0){S=S"0"};print... (0 Replies)
Hi All,
I am trying to understand and change some code written by some programmer a while ago. There are following three lines of code that I am unable to grasp. Could anybody please help me understand it?
1) cd - > /dev/null
2) fname=`basename "$1"` where $1 = /dirA/dirB/a.txt
... (3 Replies)
hi fndz.
Can you please help me with the code if I call a stored procedure from my shell script and stored procedure returns a cursor,
cursor output should be saved to a file (3 Replies)
I must write a script to change all C++ like comments:
// this is a comment
to this one
/* this is a comment */
How to do it by sed? With file:
#include <cstdio>
using namespace std; //one
// two
int main() {
printf("Example"); // three
}//four
the result should be: (2 Replies)
I often find myself grepping source code for a variable name and many times the name would be present in comment lines that I 'd prefer not to see. Do you guys know any tricks to filter out comments?
Example:
snippet of the source code
/***
* type comment 1
***/
void ... (7 Replies)
I am looking for suggestions on how I could possibly optimized that piece of code where most of the time is spend on this script. In a nutshell this is a script that creates an xml file(s) based on certain criteria that will be used by a movie jukebox.
Example of data:
$SORTEDTMP= it is a... (16 Replies)
Hi,
I am using the following code to retrieve the contents between C-style comments "/* .. */".
perl -lne 'while(/(\/\*.*?\*\/)/g) {print "$1";}'
This works fine when the commented section of code is present in a single line. But I also need to extract the data which is present inside... (3 Replies)
Hi
I am trying to find out difference between two dates with Time:Piece. I am able to get the days difference, but I want the Days as wells as hours, mins and sec difference. Below is my code for both, but the later is now working. Can anyone help me out.
With only days
use... (0 Replies)
Discussion started by: sauravrout
0 Replies
LEARN ABOUT LINUX
compile_et
COMPILE_ET(1) General Commands Manual COMPILE_ET(1)NAME
compile_et - error table compiler
SYNOPSIS
compile_et file
DESCRIPTION
Compile_et converts a table listing error-code names and associated messages into a C source file suitable for use with the com_err(3)
library.
The source file name must end with a suffix of ``.et''; the file consists of a declaration supplying the name (up to four characters long)
of the error-code table:
error_table name
followed by up to 256 entries of the form:
error_code name, " string "
and a final
end
to indicate the end of the table.
The name of the table is used to construct the name of a subroutine initialize_XXXX_error_table which must be called in order for the
com_err library to recognize the error table.
The various error codes defined are assigned sequentially increasing numbers (starting with a large number computed as a hash function of
the name of the table); thus for compatibility it is suggested that new codes be added only to the end of an existing table, and that no
codes be removed from tables.
The names defined in the table are placed into a C header file with preprocessor directives defining them as integer constants of up to 32
bits in magnitude.
A C source file is also generated which should be compiled and linked with the object files which reference these error codes; it contains
the text of the messages and the initialization subroutine. Both C files have names derived from that of the original source file, with
the ``.et'' suffix replaced by ``.c'' and ``.h''.
A ``#'' in the source file is treated as a comment character, and all remaining text to the end of the source line will be ignored.
BUGS
Since the original compile_et uses a very simple parser based on yacc(1), and this current version of compile_et uses an awk/sed combina-
tion of scripts, its error recovery leaves much to be desired.
SEE ALSO
com_err (3).
Ken Raeburn, "A Common Error Description Library for UNIX".
SIPB 30 Mar 1998 COMPILE_ET(1)
05-23-2012
