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\`");'

[Pieter Droogendijk]

On Wed, 03 Sep 2003 15:14:28 -0500
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.

--
char*x(c,k,s)ch ar*k,*s;{if(!k) return*s-36?x(0,0,s+1):s ;if(s)if(*s)c=1 0+(c?(x(
c,k,0),x(c,k+=* s-c,s+1),*k):(x(* s,k,s+1),0));el se c=10;printf(&x( ~0,0,k)[c-~-
c+"1"[~c<-c]],c);}main(){x(0 ,"^[kXc6]dn_eaoh$%c","-34*1'.+(,03#;+, )/'///*");}

[Martin Dickopp]

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

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_

#include <stdlib.h>
#include <stdio.h>

int main (void)
{
FILE *f;

f = fopen ("/tmp/foo", "w");
if (f == NULL)
{
fputs ("Cannot create /tmp/foo.\n", stderr);
return EXIT_FAILURE;
}

if (fputs ("\
all kinds of nasty stuff in here including single and double quotes\n\
and bashslashes ..\n\
(note that the here doc delimiter is preceded by a \"\\\"\n", f) == EOF
|| fclose (f) == EOF)
{
fputs ("Error writing to /tmp/foo.\n", stderr);
return EXIT_FAILURE;
}

return EXIT_SUCCESS;
}
Martin

[Dave Vandervies]

In article <20************ *************@t igris.pounder.s ol.net>,
Tom Rodman <Use-Author-Address-Header@[127.1]> wrote:

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_

Treating a chunk of text as a bash script once you've got it embedded
in your program is beyond the scope of this newsgroup (but why don't
you just create it as a separate file and use system() to ask bash to
run it?), but:

You can pack a big chunk of text nicely into a string literal by doing
something like this:
--------
const char *my_long_string =
"This is a nice long string.\n"
"Note that every line ends with a '\\n\"', and we're taking advantage\n"
"of the string-splicing feature.\n"
"Note that single quotes inside string literals don't need to be escaped.\n";
--------
You're not guaranteed to be able to embed arbitrarily long strings this
way (the Standard places a minimum on the maximum length compilers can
restrict you to, but a compiler is allowed to complain about or reject
anything beyond that minimum[1]), but in practice I'd be surprised to see
GCC (which I assume you're using) choke on any length of string literal.

Something not entirely unlike this snippet (typed directly into the editor
for my posting software, never seen a compiler, usual disclaimers apply)
might help you with escaping the double quotes and backslashes if you'd
rather not do it by hand:

--------
/*This code as posted is a demonstration-of-concept and has never seen a
compiler, let alone been tested. The usual disclaimers apply.
Output will need fixing up by hand at beginning (adding '"' at the
beginning of the first line) and end (removing '"' at the beginning of
the nonexistent just-past-last line), but should be appropriately
escaped for inclusion into C source as a big string literal otherwise.
Caller is responsible for checking ferror(in) and acting appropriately
on error.
*/
void convert_to_stri ng_literal(FILE *in,FILE *out)
{
int c;
while(c=getc(in ) != EOF)
{
switch(c)
{
case '\n':
fputs("\\n\"\n\ "",out);
break;
case '"':
fputs("\\\"",ou t);
break;
case '\\':
fputs("\\\\",ou t);
break;
default:
putc(c,out);
break;
}
}
}
--------
dave

[1] Actually, it doesn't quite even guarantee this, but the intention
is clear enough that even the DS9k implementors had to try pretty
hard to get around it.

--
Dave Vandervies dj******@csclub .uwaterloo.ca
Maybe I should add a line that says, "No matter what you do, it is sure
to annoy at least one of the regulars".
--Billy Chambless in comp.lang.c

[Dave Vandervies]

In article <20************ *************@b inky.homeunix.o rg>,
Pieter Droogendijk <gi*@binky.home unix.org> wrote:

or rephrase the
question to something not involving anything platform-specific.

Since you seem to realize that it was in fact a C question, is there any
particular reason you couldn't answer the C question instead of telling
the OP "This isn't off topic, but go away anyways"?
dave

--
Dave Vandervies dj******@csclub .uwaterloo.ca
I have neither the need, the time, or the inclination to put words into your
mouth. You are perfectly capable of damaging your reputation without any help
from me. --Richard Heathfield roasts a troll in comp.lang.c

[August Derleth]

dj******@csclub .uwaterloo.ca (Dave Vandervies) wrote in
news:bj******** **@tabloid.uwat erloo.ca on Wed 03 Sep 2003 05:34:12p:

In article <20************ *************@b inky.homeunix.o rg>,
Pieter Droogendijk <gi*@binky.home unix.org> wrote:

or rephrase the
question to something not involving anything platform-specific.

Since you seem to realize that it was in fact a C question, is there any
particular reason you couldn't answer the C question instead of telling
the OP "This isn't off topic, but go away anyways"?

Ah, but it /is/ off-topic for comp.lang.c. This group's charter is for
Standard C (C89 and C99, mainly, but K&R pre-Standard C is also acceptable
for historic reasons), and Standard C is not as platform-specific as OS
shells are. Therefore, Standard C has nothing to say about here documents,
bash, or any behaviors thereof.

Asking us to translate a snippet of platform-specific code is not only
unfair to us (who will probably give a bad answer because we don't know
the behavior of the code), but is markedly stupid behavior. It wastes your
time, our time, and the bandwidth of this newsgroup, making it less likely
that we'll /ever/ help you, even if you should stumble upon a good
question. After all, we're none of us paid for this.

[Richard Heathfield]

August Derleth wrote:

Ah, but it /is/ off-topic for comp.lang.c. This group's charter is for
Standard C

This group no Charter.

--
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

[Jack Klein]

On Thu, 04 Sep 2003 01:58:28 GMT, August Derleth
<li************ *****@onewest.n et> wrote in comp.lang.c:

dj******@csclub .uwaterloo.ca (Dave Vandervies) wrote in
news:bj******** **@tabloid.uwat erloo.ca on Wed 03 Sep 2003 05:34:12p:

In article <20************ *************@b inky.homeunix.o rg>,
Pieter Droogendijk <gi*@binky.home unix.org> wrote:

or rephrase the
question to something not involving anything platform-specific.

Since you seem to realize that it was in fact a C question, is there any
particular reason you couldn't answer the C question instead of telling
the OP "This isn't off topic, but go away anyways"?

Ah, but it /is/ off-topic for comp.lang.c. This group's charter is for

^^^^^^^

While I agree with everything you said, you are wrong where
highlighted above. This group has no charter, it started long before
there were newsgroup charters.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://www.eskimo.com/~scs/C-faq/top.html
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.l earn.c-c++ ftp://snurse-l.org/pub/acllc-c++/faq

[Jeff]

"Dave Vandervies" <dj******@csclu b.uwaterloo.ca> wrote in message
news:bj******** **@tabloid.uwat erloo.ca...

In article <20************ *************@b inky.homeunix.o rg>,
Pieter Droogendijk <gi*@binky.home unix.org> wrote:

or rephrase the
question to something not involving anything platform-specific.
Since you seem to realize that it was in fact a C question, is there any
particular reason you couldn't answer the C question instead of telling
the OP "This isn't off topic, but go away anyways"?
dave

--
Dave Vandervies

dj******@csclub .uwaterloo.ca I have neither the need, the time, or the inclination to put words into your mouth. You are perfectly capable of damaging your reputation without any help from me. --Richard Heathfield roasts a troll in

comp.lang.c
You are wrong. The OP question is clearly off-topic. Although the OP
mentioned C language in his post, he is asking a platform-specific question,
it is off-topic. We should kindly redirect him to the relevant group, it is
good for him.
--
Jeff

[Pieter Droogendijk]

On Wed, 3 Sep 2003 23:34:12 +0000 (UTC)
dj******@csclub .uwaterloo.ca (Dave Vandervies) wrote:

In article <20************ *************@b inky.homeunix.o rg>,
Pieter Droogendijk <gi*@binky.home unix.org> wrote:

or rephrase the
question to something not involving anything platform-specific.

Since you seem to realize that it was in fact a C question, is there any
particular reason you couldn't answer the C question instead of telling
the OP "This isn't off topic, but go away anyways"?

Questions to this newsgroup are topical if they are questions about Standard C
(C89/C99). This question was about translating a bash script. While he mentioned
C, it was in fact A. a homework question and B. off-topic. The first deserves
plonking and the second deserves redirection.
Giving him the option to rephrase the question to something not containing any
off-topic material, means 'translate your question to one that is topical here'
(like: how do I write text to a file).

--
char*x(c,k,s)ch ar*k,*s;{if(!k) return*s-36?x(0,0,s+1):s ;if(s)if(*s)c=1 0+(c?(x(
c,k,0),x(c,k+=* s-c,s+1),*k):(x(* s,k,s+1),0));el se c=10;printf(&x( ~0,0,k)[c-~-
c+"1"[~c<-c]],c);}main(){x(0 ,"^[kXc6]dn_eaoh$%c","-34*1'.+(,03#;+, )/'///*");}