Sponsored Content
Top Forums Programming When I am writing my own interpreter... Post 302142427 by Legend986 on Friday 26th of October 2007 05:26:17 AM
Old 10-26-2007
Well yeah.... I am using exit(1). The reason why I'm not using it here in this code is because I cannot use it in the first place... because when I'm using execlp it doesn't give me the control back....
 

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 (4 Replies)
Discussion started by: zlatan005
4 Replies

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. (5 Replies)
Discussion started by: Action
5 Replies

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. (2 Replies)
Discussion started by: cmontr
2 Replies

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... (3 Replies)
Discussion started by: sunrexstar
3 Replies

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... (2 Replies)
Discussion started by: RagingNinja
2 Replies

6. Linux

interpreter files

Can you explain me what is ment by interpreter files ?? Why and how they are used?? (1 Reply)
Discussion started by: kkalyan
1 Replies

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 (1 Reply)
Discussion started by: pandeesh
1 Replies
explain_execlp(3)					     Library Functions Manual						 explain_execlp(3)

NAME
explain_execlp - explain execlp(3) errors SYNOPSIS
#include <libexplain/execlp.h> const char *explain_execlp(, ...); const char *explain_errno_execlp(int errnum, , ...); void explain_message_execlp(char *message, int message_size, , ...); void explain_message_errno_execlp(char *message, int message_size, int errnum, , ...); DESCRIPTION
These functions may be used to obtain explanations for errors returned by the execlp(3) system call. explain_execlp const char *explain_execlp(, ...); The explain_execlp function is used to obtain an explanation of an error returned by the execlp(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. Example: This function is intended to be used in a fashion similar to the following example: if (execlp() < 0) { fprintf(stderr, "%s ", explain_execlp()); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_execlp_or_die(3) function. explain_errno_execlp const char *explain_errno_execlp(int errnum, , ...); The explain_errno_execlp function is used to obtain an explanation of an error returned by the execlp(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. Returns: The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads. Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library. Example: This function is intended to be used in a fashion similar to the following example: if (execlp() < 0) { int err = errno; fprintf(stderr, "%s ", explain_errno_execlp(err, )); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_execlp_or_die(3) function. explain_message_execlp void explain_message_execlp(char *message, int message_size, , ...); The explain_message_execlp function is used to obtain an explanation of an error returned by the execlp(3) system call. The least the mes- sage will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. The errno global variable will be used to obtain the error value to be decoded. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. Example: This function is intended to be used in a fashion similar to the following example: if (execlp() < 0) { char message[3000]; explain_message_execlp(message, sizeof(message), ); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_execlp_or_die(3) function. explain_message_errno_execlp void explain_message_errno_execlp(char *message, int message_size, int errnum, , ...); The explain_message_errno_execlp function is used to obtain an explanation of an error returned by the execlp(3) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail. message The location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe. message_size The size in bytes of the location in which to store the returned message. errnum The error value to be decoded, usually obtained from the errno global variable just before this function is called. This is neces- sary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno. Example: This function is intended to be used in a fashion similar to the following example: if (execlp() < 0) { int err = errno; char message[3000]; explain_message_errno_execlp(message, sizeof(message), err, ); fprintf(stderr, "%s ", message); exit(EXIT_FAILURE); } The above code example is available pre-packaged as the explain_execlp_or_die(3) function. SEE ALSO
execlp(3) execute a file explain_execlp_or_die(3) execute a file and report errors COPYRIGHT
libexplain version 0.52 Copyright (C) 2009 Peter Miller explain_execlp(3)
All times are GMT -4. The time now is 03:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy