14341

Hi All,

I have the following file.
$ cat test
#include "asd.h"
#include "awr.h"
#include "asfa.h"

case 1:

$ cat test | sed -e 's/i/I/g' -e 's/n/N/g/ >test

$cat test
#INclude "asd.h"
#INclude "awr.h"
#INclude "asfa.h"

case 2:

$ cat test | sed -e 's!\(#include\)[[:space:]]*\(.*\)!\1 \2!' -e 's!#include\ \"asd.h\"!#include\ \"ded.h\"!' >test

$ cat test
$

In case 2 the file "test" is blank.

Can anyone tell me why the file is balnked out in case-2 whereas it is not in case1?

I am using FreeBSD 6.3 and using BASH shell

Thanks,
14341

Kennedy

I would guess that it has something to do with your parans, but I don't know off the top of my head and I'd have to test what you've done to figure out what it is actually doing. What are you attempting to do? If you give us that, then we can probably help you get the correct sed script.

14341

I need to write a shell script that automatically changes the header file in a given list of files.

I will be given a list of files containing "from.h"

They will provide another header file say "to.h"

Now i need to replace *#include "from.h"* with *#include "to.h"* in the list of input files.

Kennedy

Hmm, sounds like homework to me. You want to do this in a shell script. Take the script and make sure you know how to parse the command line. I would create a usage() that told the user to use something like OLD=bla.h NEW=cool.h or the like. After that, all other strings on the command line are files that need to be updated. It is a simple for loop to do this.

Post your code (when you get some) and we'll help you the rest of the way.

brewbuck

Your script works fine. It's the directing the output to the same file it came from which destroys the result. Don't do that.

And your first example does not work. It should be this:

And if you try that, you see that it destroys the input as well. Directing out to the same file as the input is wrong.

(The reason why is pretty obvious. Shell pipelines are launched from right to left. The first thing that happens is all the fifos are created. Then sed gets launched, with output directed to 'test'. 'test' is opened in O_WRONLY mode, which destroys it. By the time cat starts up, the input file is already gone)

EDIT: Even if you remove the completely extraneous cat ( cat x | sed -e r can always be replaced with sed -e r x ) it still kills the input, again, because the shell opens the redirect before doing anything else)

__________________
"Congratulations on your purchase. To begin using your quantum computer, set the power switch to both off and on simultaneously." -- raftpeople@slashdot

14341

Thank you for the reply........

I once again checked the two cases and i see that the result is inconsistent. Sometimes the output file is not blank and output's the result after sed's substitution.

i donno that shell open's the redirect first before processing.

Thank you,
14341