Sponsored Content
Full Discussion: Major File Reformat
Top Forums Shell Programming and Scripting Major File Reformat Post 302586442 by Blue Solo on Monday 2nd of January 2012 03:05:55 AM
Old 01-02-2012
You are a genius and I am envious of your abilities. It took me longer to write my original post than took you to respond with a solution.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

reformat the file

Hi all, I ran into this problem, hope you can help I have a text file like this: Spriden ID First Name Last Name Term Code Detail Code Amount Trans Date Description ... (3 Replies)
Discussion started by: CamTu
3 Replies

2. Shell Programming and Scripting

Reformat Crontab file

I need help writing a script that will reformat a crontab file. The first thing the script is doing is a crontab -l > crontab.txt. I need the crontab.txt file to read "8.00 PM every weekday (Mon-Fri) only in Oct." instead of the orig format "0 20 * 10 1-5" (1 Reply)
Discussion started by: alnita
1 Replies

3. Programming

which head file for major and minor function?

#include <sys/types.h> #include <sys/stat.h> #include <sys/termios.h> #include <stdio.h> #include <stdlib.h> #include <stddef.h> #include <string.h> #include <unistd.h> #include <signal.h> #include <sys/mkdev.h> int main(int argc, char *argv) { int i; struct stat buf; ... (4 Replies)
Discussion started by: konvalo
4 Replies

4. Shell Programming and Scripting

Please help me reformat this file

I am working with a file of the form; 4256 7726 1 6525 716 1 7626 0838 1 8726 7623 2 8625 1563 2 1662 2628 3 1551 3552 3 1542 7984 ... (3 Replies)
Discussion started by: digipak
3 Replies

5. Shell Programming and Scripting

Reformat a file

I have a csv file with 11 columns. The first columns contains the User Id. One User id can have multiple sub Id. The value of Sub Id is in column 10. 100026,captjason@hawaii.rr.com ,jason ,wolford ,1/16/1969, ,US, ,96761 ,15 ,seg_id 100026,captjason@hawaii.rr.com ,jason ,wolford ,1/16/1969,... (3 Replies)
Discussion started by: r_t_1601
3 Replies

6. Shell Programming and Scripting

Reformat file using nawk

Hi all, I have a file with records that look something like this, "Transaction ID",Date,Email,"Card Type",Amount,"NETBANX Ref","Root Ref","Transaction Type","Merchant Ref",Status,"Interface ID","Interface Name","User ID" nnnnnnnnn,"21 Nov 2011 00:10:47",someone@hotmail.co.uk,"Visa... (2 Replies)
Discussion started by: dazedandconfuse
2 Replies

7. Shell Programming and Scripting

awk reformat file

Hello: When I tried a perl-oneliner to re-format fasta file. infile.fasta >YAL069W-1.334 Putative promoter CCACACCACACCCACACACC ACACCACACCCACACACACA ACAGCCCTAATCTAACCC >YAL068C-7235.2170 Putative ABC sequence TACGAGAATAATTT ACGTAAATGAAGTT TATATATAAA >gi|31044174|gb|AY143560.1|... (15 Replies)
Discussion started by: yifangt
15 Replies

8. Shell Programming and Scripting

[Solved] File reformat

I am using the code below to reformat the input (hp.txt). The output (newhp.txt) is not in the desired format and I can not seem to figure it out. I have attached both. Thank you. perl -aF/\\t/ -lne 'print join(" ",@F) for ("0 A","0 G","0 C","0 T","A 0","G 0","C 0","T 0")' hp.txt > newhp.txt ... (4 Replies)
Discussion started by: cmccabe
4 Replies

9. Shell Programming and Scripting

Reformat csv file

Hi, I have a csv file with content like: 1,0,100 1,1,150 2,0,200 2,1,250 3,0,300 3,1,350 I want an output such that all numbers in 3rd col where 2nd col is "0" come in the same col in the output. The same goes for numbers where 2nd col is "1". 1 100 150 2 200 250 3 300 350 Tnx... (2 Replies)
Discussion started by: jamaje
2 Replies

10. Shell Programming and Scripting

awk to reformat output if input file is empty, but not if file has data in it

The below awk improved bu @MadeInGermany, works great as long as the input file has data in it in the below format: input chrX 25031028 25031925 chrX:25031028-25031925 ARX 631 18 chrX 25031028 25031925 chrX:25031028-25031925 ARX 632 14... (3 Replies)
Discussion started by: cmccabe
3 Replies
Hook::LexWrap(3)					User Contributed Perl Documentation					  Hook::LexWrap(3)

NAME
Hook::LexWrap - Lexically scoped subroutine wrappers VERSION
This document describes version 0.23 of Hook::LexWrap. SYNOPSIS
use Hook::LexWrap; sub doit { print "[doit:", caller, "]"; return {my=>"data"} } SCOPED: { wrap doit, pre => sub { print "[pre1: @_] " }, post => sub { print "[post1:@_] "; $_[1]=9; }; my $temporarily = wrap doit, post => sub { print "[post2:@_] " }, pre => sub { print "[pre2: @_] "}; @args = (1,2,3); doit(@args); # pre2->pre1->doit->post1->post2 } @args = (4,5,6); doit(@args); # pre1->doit->post1 DESCRIPTION
Hook::LexWrap allows you to install a pre- or post-wrapper (or both) around an existing subroutine. Unlike other modules that provide this capacity (e.g. Hook::PreAndPost and Hook::WrapSub), Hook::LexWrap implements wrappers in such a way that the standard "caller" function works correctly within the wrapped subroutine. To install a prewrappers, you write: use Hook::LexWrap; wrap 'subroutine_name', pre => &some_other_sub; #or: wrap *subroutine_name, pre => &some_other_sub; The first argument to "wrap" is a string containing the name of the subroutine to be wrapped (or the typeglob containing it, or a reference to it). The subroutine name may be qualified, and the subroutine must already be defined. The second argument indicates the type of wrapper being applied and must be either 'pre' or 'post'. The third argument must be a reference to a subroutine that implements the wrapper. To install a post-wrapper, you write: wrap 'subroutine_name', post => &yet_another_sub; #or: wrap *subroutine_name, post => &yet_another_sub; To install both at once: wrap 'subroutine_name', pre => &some_other_sub, post => &yet_another_sub; or: wrap *subroutine_name, post => &yet_another_sub, # order in which wrappers are pre => &some_other_sub; # specified doesn't matter Once they are installed, the pre- and post-wrappers will be called before and after the subroutine itself, and will be passed the same argument list. The pre- and post-wrappers and the original subroutine also all see the same (correct!) values from "caller" and "wantarray". Short-circuiting and long-circuiting return values The pre- and post-wrappers both receive an extra argument in their @_ arrays. That extra argument is appended to the original argument list (i.e. is can always be accessed as $_[-1]) and acts as a place-holder for the original subroutine's return value. In a pre-wrapper, $_[-1] is -- for obvious reasons -- "undef". However, $_[-1] may be assigned to in a pre-wrapper, in which case Hook::LexWrap assumes that the original subroutine has been "pre-empted", and that neither it, nor the corresponding post-wrapper, nor any wrappers that were applied before the pre-empting pre-wrapper was installed, need be run. Note that any post-wrappers that were installed after the pre-empting pre-wrapper was installed will still be called before the original subroutine call returns. In a post-wrapper, $_[-1] contains the return value produced by the wrapped subroutine. In a scalar return context, this value is the scalar return value. In an list return context, this value is a reference to the array of return values. $_[-1] may be assigned to in a post-wrapper, and this changes the return value accordingly. Access to the arguments and return value is useful for implementing techniques such as memoization: my %cache; wrap fibonacci, pre => sub { $_[-1] = $cache{$_[0]} if $cache{$_[0]} }, post => sub { $cache{$_[0]} = $_[-1] }; or for converting arguments and return values in a consistent manner: # set_temp expects and returns degrees Fahrenheit, # but we want to use Celsius wrap set_temp, pre => sub { splice @_, 0, 1, $_[0] * 1.8 + 32 }, post => sub { $_[-1] = ($_[0] - 32) / 1.8 }; Lexically scoped wrappers Normally, any wrappers installed by "wrap" remain attached to the subroutine until it is undefined. However, it is possible to make specific wrappers lexically bound, so that they operate only until the end of the scope in which they're created (or until some other specific point in the code). If "wrap" is called in a non-void context: my $lexical = wrap 'sub_name', pre => &wrapper; it returns a special object corresponding to the particular wrapper being placed around the original subroutine. When that object is destroyed -- when its container variable goes out of scope, or when its reference count otherwise falls to zero (e.g. "undef $lexical"), or when it is explicitly destroyed ("$lexical->DESTROY") -- the corresponding wrapper is removed from around the original subroutine. Note, however, that all other wrappers around the subroutine are preserved. Anonymous wrappers If the subroutine to be wrapped is passed as a reference (rather than by name or by typeglob), "wrap" does not install the wrappers around the original subroutine. Instead it generates a new subroutine which acts as if it were the original with those wrappers around it. It then returns a reference to that new subroutine. Only calls to the original through that wrapped reference invoke the wrappers. Direct by- name calls to the original, or calls through another reference, do not. If the original is subsequently wrapped by name, the anonymously wrapped subroutine reference does not see those wrappers. In other words, wrappers installed via a subroutine reference are completely independent of those installed via the subroutine's name (or typeglob). For example: sub original { print "ray" } # Wrap anonymously... my $anon_wrapped = wrap &original, pre => sub { print "do..." }; # Show effects... original(); # prints "ray" $anon_wrapped->(); # prints "do..ray" # Wrap nonymously... wrap *original, pre => sub { print "fa.." }, post => sub { print "..mi" }; # Show effects... original(); # now prints "fa..ray..mi" $anon_wrapped->(); # still prints "do...ray" DIAGNOSTICS
"Can't wrap non-existent subroutine %s" An attempt was made to wrap a subroutine that was not defined at the point of wrapping. "'pre' value is not a subroutine reference" The value passed to "wrap" after the 'pre' flag was not a subroutine reference. Typically, someone forgot the "sub" on the anonymous subroutine: wrap 'subname', pre => { your_code_here() }; and Perl interpreted the last argument as a hash constructor. "'post' value is not a subroutine reference" The value passed to "wrap" after the 'post' flag was not a subroutine reference. "Uselessly wrapped subroutine reference in void context" (warning only) When the subroutine to be wrapped is passed as a subroutine reference, "wrap" does not install the wrapper around the original, but instead returns a reference to a subroutine which wraps the original (see "Anonymous wrappers"). However, there's no point in doing this if you don't catch the resulting subroutine reference. AUTHOR
Damian Conway (damian@conway.org) BLAME
Schwern made me do this (by implying it wasn't possible ;-) BUGS
There are undoubtedly serious bugs lurking somewhere in code this funky :-) Bug reports and other feedback are most welcome. SEE ALSO
Sub::Prepend COPYRIGHT
Copyright (c) 2001, Damian Conway. All Rights Reserved. This module is free software. It may be used, redistributed and/or modified under the same terms as Perl itself. perl v5.16.2 2013-08-25 Hook::LexWrap(3)
All times are GMT -4. The time now is 12:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy