When I am writing my own interpreter... Post: 302142013

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

an command interpreter

if somebody can help me pls. i need the source code for a shell which compiles C or java programs. i need a very short and simple one, just for the compiling part, in UNIX Respect

2. UNIX for Dummies Questions & Answers

m4 as script interpreter

#!/usr/bin/m4 when running m4 scripts with "#!/usr/bin/m4" they are executed properly, but "#!/usr/bin/m4" is printed out - how to avoid it? Thanks in advance.

3. Programming

Java Interpreter

Hello guys - do you have any sample program implementing UNIX commands in an interpreter with Java? I can look up the simple ones such "ls" etc and then write my own commands. I would appreciate it.

4. Shell Programming and Scripting

Multiple interpreter declarations

Hi, I am writing a shell script that connects to a remote server and performs some tasks on the server and exits. Since i am using a ssh connection, i am using a "expect" utility to supply the password automatically (which is present within the script). In order to use this utility, i need to...

5. Shell Programming and Scripting

Bad Interpreter

Hi. My name is Caleb (a.k.a RagingNinja) form the whited00r forums. (Whited00r makes custom firmware for iOS devices). I have been learning and creating simple shells scripts. I have been recently using VIM for Windows or using VirtualBox to run the UBUNTU OS within VirtualBox to create my shell...

6. Linux

interpreter files

Can you explain me what is ment by interpreter files ?? Why and how they are used??

7. Shell Programming and Scripting

Dynamically choosing the interpreter

Hi, Is it possible to choose the inerpreter conditionally. For example, if whereis bash returns /usr/bin/bash then i need to choose #!/usr/bin/bash else i need to use #!/usr/bin/sh. Is it possible to achieve in a shell script? Thanks

LEARN ABOUT OPENDARWIN

pipe

PIPE(2) 						      BSD System Calls Manual							   PIPE(2)

NAME

     pipe -- create descriptor pair for interprocess communication

SYNOPSIS

     #include <unistd.h>

     int
     pipe(int *fildes);

DESCRIPTION

     The pipe() function creates a pipe, which is an object allowing unidirectional data flow, and allocates a pair of file descriptors.  The
     first descriptor connects to the read end of the pipe, and the second connects to the write end, so that data written to fildes[1] appears on
     (i.e., can be read from) fildes[0].  This allows the output of one program to be sent to another program: the source's standard output is set
     up to be the write end of the pipe, and the sink's standard input is set up to be the read end of the pipe.  The pipe itself persists until
     all its associated descriptors are closed.

     A pipe whose read or write end has been closed is considered widowed.  Writing on such a pipe causes the writing process to receive a SIGPIPE
     signal.  Widowing a pipe is the only way to deliver end-of-file to a reader: after the reader consumes any buffered data, reading a widowed
     pipe returns a zero count.

RETURN VALUES

     On successful creation of the pipe, zero is returned. Otherwise, a value of -1 is returned and the variable errno set to indicate the error.

ERRORS

     The pipe() call will fail if:

     [EMFILE]		Too many descriptors are active.

     [ENFILE]		The system file table is full.

     [EFAULT]		The fildes buffer is in an invalid area of the process's address space.

SEE ALSO

     sh(1), read(2), write(2), fork(2), socketpair(2)

HISTORY

     A pipe() function call appeared in Version 6 AT&T UNIX.

4th Berkeley Distribution					   June 4, 1993 					 4th Berkeley Distribution