Sponsored Content
Full Discussion: SED code to AWK
Top Forums Shell Programming and Scripting SED code to AWK Post 302675843 by sanantonio7777 on Monday 23rd of July 2012 04:15:18 PM
Old 07-23-2012
OS X 10.5

yeah it works on GNU but on OS X?...

any ideas for the code?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

AWK or SED

Hi Can some tell to use AWK or SED in the following situtation file A has 10 columns, whenever column 10 has valuues AorBorCorDorE replace the column value with X else if it has GorH replace the column value with Y. I'm not too user which one to use, whether mix of both of anone wil do ? ... (7 Replies)
Discussion started by: braindrain
7 Replies

2. UNIX for Advanced & Expert Users

sed in awk ? or nested awk ?

Hey all, Can I put sed command inside the awk action ?? If not then can i do grep in the awk action ?? For ex: awk '$1=="174" { ppid=($2) ; sed -n '/$ppid/p' tempfind.txt ; }' tempfind.txt Assume: 174 is string. Assume: tempfind.txt is used for awk and sed both. tempfind.txt... (11 Replies)
Discussion started by: varungupta
11 Replies

3. Shell Programming and Scripting

awk/sed help

$ cat file "" """ "dasdd" "fdsfs"Fsd"fs "aa"sss"dsadd"" Is there a way using awk or sed to print the lines which contain 3 or more " i.e. required output: """ "fdsfs"Fsd"fs "aa"sss"dsadd"" I tried to find a solution, but no luck, please help (4 Replies)
Discussion started by: jkl_jkl
4 Replies

4. Shell Programming and Scripting

help in sed or awk

Hi, I have a file paths.txt with data: http://test/data/table/data - common http://test/data/table/data/common - common http://test/data/table/db/abc.txt - common http://test/data/table/db/xyz.txt - common http://test/data/table/abc I want to extract everything after... (2 Replies)
Discussion started by: muaz
2 Replies

5. Shell Programming and Scripting

What to use : awk or sed

Hi All, I am a bit confused,Can anyone help; My problem is that i have a flat file in this format 8.10 USAccountSummaryClone1 3.10 USAccountSummaryClone2 2.80 GlobalUserManagementClone1 2.10 BasicServicesClone2 1.60 MYCAServicesClone2 1.30 INTLEStatementClone1 0.90... (6 Replies)
Discussion started by: usha rao
6 Replies

6. Shell Programming and Scripting

awk or sed help

Hi Help, I hope you guys are doing good! I have an input file which looks like 11 12 13 16 17 |$678.09 78 p| 11 12 13 16 17 | 8.09278 p| 11 12 13 16 17 |3678 | I want the op file to look like $678.09078p0008.09278p36780000000 i.e only to print the characters within... (4 Replies)
Discussion started by: Indra2011
4 Replies

7. Shell Programming and Scripting

sed and awk giving error ./sample.sh: line 13: sed: command not found

Hi, I am running a script sample.sh in bash environment .In the script i am using sed and awk commands which when executed individually from terminal they are getting executed normally but when i give these sed and awk commands in the script it is giving the below errors :- ./sample.sh: line... (12 Replies)
Discussion started by: satishmallidi
12 Replies

8. Shell Programming and Scripting

Retrieve information Text/Word from HTML code using awk/sed

awk/sed newbie here. I have a HTML file and from that file and I would like to retrieve a text word. <font face=arial size=-1><li><a href=/value_for_clients/Tokyo/abc_process.txt>abc</a> NDK Version: 4.0 </li> <font face=arial size=-1><li><a... (6 Replies)
Discussion started by: sk2code
6 Replies

9. UNIX for Dummies Questions & Answers

sed or awk

my data looks like this: "Jean Marie","Carroll",carrollj@yahoo.com all said and done, i'd like to see like this: "Jean Marie" "Caroll" carroll@yahoo.com This user will be unable to respond to requests for more information for a couple of weeks due to continually refusing to use... (8 Replies)
Discussion started by: lawsongeek
8 Replies

10. Shell Programming and Scripting

Using sed or awk

I have a .txt file with almost few hundreds interfaces address which need to be changed or mapped to the new interface naming convention. for e.g interface xe-8/0/0 should be xe-16/0/0 xe-9/0/0 should be xe-17/0/0 it keeps going to xe-31/0/0 which should become xe-55/0/0. i wanted to know... (12 Replies)
Discussion started by: Jared
12 Replies
Pod::Simple::PullParser(3)				User Contributed Perl Documentation				Pod::Simple::PullParser(3)

NAME
Pod::Simple::PullParser -- a pull-parser interface to parsing Pod SYNOPSIS
my $parser = SomePodProcessor->new; $parser->set_source( "whatever.pod" ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( $some_filehandle_object ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( $document_source ); $parser->run; Or: my $parser = SomePodProcessor->new; $parser->set_source( @document_lines ); $parser->run; And elsewhere: require 5; package SomePodProcessor; use strict; use base qw(Pod::Simple::PullParser); sub run { my $self = shift; Token: while(my $token = $self->get_token) { ...process each token... } } DESCRIPTION
This class is for using Pod::Simple to build a Pod processor -- but one that uses an interface based on a stream of token objects, instead of based on events. This is a subclass of Pod::Simple and inherits all its methods. A subclass of Pod::Simple::PullParser should define a "run" method that calls "$token = $parser->get_token" to pull tokens. See the source for Pod::Simple::RTF for an example of a formatter that uses Pod::Simple::PullParser. METHODS
my $token = $parser->get_token This returns the next token object (which will be of a subclass of Pod::Simple::PullParserToken), or undef if the parser-stream has hit the end of the document. $parser->unget_token( $token ) $parser->unget_token( $token1, $token2, ... ) This restores the token object(s) to the front of the parser stream. The source has to be set before you can parse anything. The lowest-level way is to call "set_source": $parser->set_source( $filename ) $parser->set_source( $filehandle_object ) $parser->set_source( $document_source ) $parser->set_source( @document_lines ) Or you can call these methods, which Pod::Simple::PullParser has defined to work just like Pod::Simple's same-named methods: $parser->parse_file(...) $parser->parse_string_document(...) $parser->filter(...) $parser->parse_from_file(...) For those to work, the Pod-processing subclass of Pod::Simple::PullParser has to have defined a $parser->run method -- so it is advised that all Pod::Simple::PullParser subclasses do so. See the Synopsis above, or the source for Pod::Simple::RTF. Authors of formatter subclasses might find these methods useful to call on a parser object that you haven't started pulling tokens from yet: my $title_string = $parser->get_title This tries to get the title string out of $parser, by getting some tokens, and scanning them for the title, and then ungetting them so that you can process the token-stream from the beginning. For example, suppose you have a document that starts out: =head1 NAME Hoo::Boy::Wowza -- Stuff B<wow> yeah! $parser->get_title on that document will return "Hoo::Boy::Wowza -- Stuff wow yeah!". If the document starts with: =head1 Name Hoo::Boy::W00t -- Stuff B<w00t> yeah! Then you'll need to pass the "nocase" option in order to recognize "Name": $parser->get_title(nocase => 1); In cases where get_title can't find the title, it will return empty-string (""). my $title_string = $parser->get_short_title This is just like get_title, except that it returns just the modulename, if the title seems to be of the form "SomeModuleName -- description". For example, suppose you have a document that starts out: =head1 NAME Hoo::Boy::Wowza -- Stuff B<wow> yeah! then $parser->get_short_title on that document will return "Hoo::Boy::Wowza". But if the document starts out: =head1 NAME Hooboy, stuff B<wow> yeah! then $parser->get_short_title on that document will return "Hooboy, stuff wow yeah!". If the document starts with: =head1 Name Hoo::Boy::W00t -- Stuff B<w00t> yeah! Then you'll need to pass the "nocase" option in order to recognize "Name": $parser->get_short_title(nocase => 1); If the title can't be found, then get_short_title returns empty-string (""). $author_name = $parser->get_author This works like get_title except that it returns the contents of the "=head1 AUTHOR Paragraph... " section, assuming that that section isn't terribly long. To recognize a "=head1 Author Paragraph " section, pass the "nocase" otpion: $parser->get_author(nocase => 1); (This method tolerates "AUTHORS" instead of "AUTHOR" too.) $description_name = $parser->get_description This works like get_title except that it returns the contents of the "=head1 DESCRIPTION Paragraph... " section, assuming that that section isn't terribly long. To recognize a "=head1 Description Paragraph " section, pass the "nocase" otpion: $parser->get_description(nocase => 1); $version_block = $parser->get_version This works like get_title except that it returns the contents of the "=head1 VERSION [BIG BLOCK] " block. Note that this does NOT return the module's $VERSION!! To recognize a "=head1 Version [BIG BLOCK] " section, pass the "nocase" otpion: $parser->get_version(nocase => 1); NOTE
You don't actually have to define a "run" method. If you're writing a Pod-formatter class, you should define a "run" just so that users can call "parse_file" etc, but you don't have to. And if you're not writing a formatter class, but are instead just writing a program that does something simple with a Pod::PullParser object (and not an object of a subclass), then there's no reason to bother subclassing to add a "run" method. SEE ALSO
Pod::Simple Pod::Simple::PullParserToken -- and its subclasses Pod::Simple::PullParserStartToken, Pod::Simple::PullParserTextToken, and Pod::Simple::PullParserEndToken. HTML::TokeParser, which inspired this. SUPPORT
Questions or discussion about POD and Pod::Simple should be sent to the pod-people@perl.org mail list. Send an empty email to pod-people-subscribe@perl.org to subscribe. This module is managed in an open GitHub repository, <https://github.com/theory/pod-simple/>. Feel free to fork and contribute, or to clone <git://github.com/theory/pod-simple.git> and send patches! Patches against Pod::Simple are welcome. Please send bug reports to <bug-pod-simple@rt.cpan.org>. COPYRIGHT AND DISCLAIMERS
Copyright (c) 2002 Sean M. Burke. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. AUTHOR
Pod::Simple was created by Sean M. Burke <sburke@cpan.org>. But don't bother him, he's retired. Pod::Simple is maintained by: o Allison Randal "allison@perl.org" o Hans Dieter Pearcey "hdp@cpan.org" o David E. Wheeler "dwheeler@cpan.org" perl v5.16.3 2013-05-03 Pod::Simple::PullParser(3)
All times are GMT -4. The time now is 03:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy