want a "here doc" equivalent in "c"

[Tom Rodman]

I want to embed a bash script inside the c program.

How could you do the below bash snippet in "c"?:

cat > /tmp/foo <<\__EOD_
all kinds of nasty stuff in here including single and double quotes
and bashslashes ..
(note that the here doc delimiter is preceded by a "\"
__EOD_

--
regards,
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "1\:6UP\,\$\!T\ <F\]D\;6\%N\+F\-O\;0H\`");'

[Richard Heathfield]

August Derleth wrote:

Richard Heathfield <do******@addre ss.co.uk.invali d> wrote in
news:bj******** **@hercules.bti nternet.com on Thu 04 Sep 2003 06:34:49p:
<snip>

Which FAQ tells them that VisualAda++ is off-topic here? I don't think
the word "topic" is even mentioned in the FAQ. It certainly doesn't
appear in the index of the book version.

http://www.eskimo.com/~scs/C-faq/q19.1.html -- First topic in the section
System Dependencies. It says:

"Since comp.lang.c is oriented towards topics that C does deal with, you
will usually get better answers to these questions by referring to a
system-specific newsgroup such as comp.unix.quest ions or
comp.os.msdos.p rogrammer, and to the FAQ lists for these groups."

I don't suppose I should be too surprised that this sentence doesn't appear
in my paper edition. Clearly, it's been edited out as being irrelevant to
casual purchasers.
It isn't as hardassed as most clc regs are, but it does gently state that
we deal with Standard C, not Ada, not Pascal, not system-specific
extensions to C.
Yes, that's a fair point.
And if we see a post about VisualAda++, we will storm Redmond and shove
the One Boot up the Gates of Hell.
Why wait for a post about VisualAda++? If it feels good, do it.
So was I wrong? Yes, I was. Will I admit that? No, not really. I can still
quote mostly-relevant portions of the FAQ and appeal to the common sense
of Usenetters.

The common sense of Usenetters? You're new here, right? ;-)
--
Richard Heathfield : bi****@eton.pow ernet.co.uk
"Usenet is a strange place." - Dennis M Ritchie, 29 July 1999.
C FAQ: http://www.eskimo.com/~scs/C-faq/top.html
K&R answers, C books, etc: http://users.powernet.co.uk/eton

[Richard Heathfield]

August Derleth wrote:

Richard Heathfield <do******@addre ss.co.uk.invali d> wrote in
news:bj******** **@hercules.bti nternet.com on Thu 04 Sep 2003 03:41:19p:

Alan Balmer wrote:
Some of us prefer the group /not/ to have a charter, not least because
of the Schadenfreude that inevitably results from someone thoughtlessly
suggesting that we refer to it.

And I might write one, just for the Schadenfreude that will result when
someone smugly says that we don't have one.

But since any charter you write would be yours, not ours, the Schadenfreude
would be ours, not yours.

--
Richard Heathfield : bi****@eton.pow ernet.co.uk
"Usenet is a strange place." - Dennis M Ritchie, 29 July 1999.
C FAQ: http://www.eskimo.com/~scs/C-faq/top.html
K&R answers, C books, etc: http://users.powernet.co.uk/eton

[LibraryUser]

Pieter Droogendijk wrote:

Tom Rodman <Use-Author-Address-Header@[127.1]> wrote:

I want to embed a bash script inside the c program.

Standard C knows nothing of 'embed', 'bash' or 'script'.

How could you do the below bash snippet in "c"?:

cat > /tmp/foo <<\__EOD_
all kinds of nasty stuff in here including single and
double quotes and bashslashes ..
(note that the here doc delimiter is preceded by a "\"
__EOD_

Ask this in comp.unix.progr ammer and prepare to be helped, or
rephrase the question to something not involving anything
platform-specific.

It is a perfectly valid C question, even though he is describing
the off-topic eventual use. The real question is "how to embed
all those characters within C source code", and the answer is to
use the escape character '\'.

--
Replies should be to the newsgroup
Chuck Falconer, on vacation.

[Alan Balmer]

On Fri, 05 Sep 2003 02:51:45 GMT, August Derleth
<li************ *****@onewest.n et> wrote:

Richard Heathfield <do******@addre ss.co.uk.invali d> wrote in
news:bj******* ***@hercules.bt internet.com on Thu 04 Sep 2003 03:41:19p:

Alan Balmer wrote:
Some of us prefer the group /not/ to have a charter, not least because
of the Schadenfreude that inevitably results from someone thoughtlessly
suggesting that we refer to it.

I might wish I had written the above, but it was actually Richard.
And I might write one, just for the Schadenfreude that will result when
someone smugly says that we don't have one.

... grumble grumble grumble ...

--
Al Balmer
Balmer Consulting
re************* ***********@att .net

[LibraryUser]

Pieter Droogendijk wrote:

Tom Rodman <Use-Author-Address-Header@[127.1]> wrote:

I want to embed a bash script inside the c program.

Standard C knows nothing of 'embed', 'bash' or 'script'.

How could you do the below bash snippet in "c"?:

cat > /tmp/foo <<\__EOD_
all kinds of nasty stuff in here including single and
double quotes and bashslashes ..
(note that the here doc delimiter is preceded by a "\"
__EOD_

Ask this in comp.unix.progr ammer and prepare to be helped, or
rephrase the question to something not involving anything
platform-specific.

It is a perfectly valid C question, even though he is describing
the off-topic eventual use. The real question is "how to embed
all those characters within C source code", and the answer is to
use the escape character '\'.

--
Replies should be to the newsgroup
Chuck Falconer, on vacation.

[Tom Rodman]

Derk:

Thanks for your help - I'll use your approach; will write a
shell script filter to generate the meta-quoted strings in text[].

--
regards,
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "1\:6UP\,\$\!T\ <F\]D\;6\%N\+F\-O\;0H\`");'

Derk wrote:
<snip>

char *text[] = {
/*X*/
"line 1\n",
"line 2\n",
...,
"line n\n",
/*Y*/
0
};
<snip>The lines between X and Y have to have quotes and backslashes backslashed escaped,
besides the initial '"' and trailing 'n",' for each line. It's a pain to do this
by hand. It's easy to write a simple filter for this and then do something like
herefilter <textfile >textfile.her e
and replace the /*X*/.../*Y*/ with
#include "textfile.h ere"

I do something similar quite often to insert Tcl scripts into C programs
with the makefile calling the filter and compiling the file.

[Alan Balmer]

On Fri, 05 Sep 2003 02:51:45 GMT, August Derleth
<li************ *****@onewest.n et> wrote:

Richard Heathfield <do******@addre ss.co.uk.invali d> wrote in
news:bj******* ***@hercules.bt internet.com on Thu 04 Sep 2003 03:41:19p:

Alan Balmer wrote:
Some of us prefer the group /not/ to have a charter, not least because
of the Schadenfreude that inevitably results from someone thoughtlessly
suggesting that we refer to it.

I might wish I had written the above, but it was actually Richard.
And I might write one, just for the Schadenfreude that will result when
someone smugly says that we don't have one.

... grumble grumble grumble ...

--
Al Balmer
Balmer Consulting
re************* ***********@att .net

[Tom Rodman]

Derk:

Thanks for your help - I'll use your approach; will write a
shell script filter to generate the meta-quoted strings in text[].

--
regards,
Tom Rodman
pls run for my address:
perl -e 'print unpack("u", "1\:6UP\,\$\!T\ <F\]D\;6\%N\+F\-O\;0H\`");'

Derk wrote:
<snip>

char *text[] = {
/*X*/
"line 1\n",
"line 2\n",
...,
"line n\n",
/*Y*/
0
};
<snip>The lines between X and Y have to have quotes and backslashes backslashed escaped,
besides the initial '"' and trailing 'n",' for each line. It's a pain to do this
by hand. It's easy to write a simple filter for this and then do something like
herefilter <textfile >textfile.her e
and replace the /*X*/.../*Y*/ with
#include "textfile.h ere"

I do something similar quite often to insert Tcl scripts into C programs
with the makefile calling the filter and compiling the file.