06-18-2008
i just need the source code of a simple command interpreder for compiling c programs in unix
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I have a developer that is trying to start a script with sh "scriptname". In the script, he is specifying #!/usr/bin/ksh as the command interpreter. For some reason sh is ignoring the #!/usr/bin/ksh. We are running Solaris 8. Does anyone have any ideas what could be causing this? Here... (3 Replies)
Discussion started by: ckeith79
3 Replies
2. Programming
While trying out my hand at writing an interpreter, I was wondering about a a few issues one of which is the following: When I run a command such as jobs in the shell, I get a list of all the background jobs that are running... But if I need my interpreter to run that command, how would I be doing... (34 Replies)
Discussion started by: Legend986
34 Replies
3. UNIX for Dummies Questions & Answers
#!/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
4. Programming
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
5. Shell Programming and Scripting
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
6. Shell Programming and Scripting
Hello everybody!
I have a problem "Write script, which will display the actual number of bash command interpreter, working in the operating system." I used ps command to list all process running in the system but I don't know how to select only bash command interpreter. Pls give me some... (3 Replies)
Discussion started by: nguyendu0102
3 Replies
7. Shell Programming and Scripting
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
8. Linux
Can you explain me what is ment by interpreter files ??
Why and how they are used?? (1 Reply)
Discussion started by: kkalyan
1 Replies
9. Shell Programming and Scripting
Hello senior members,
I am a fairly newbie here. I just want to ask one question that how can once create one's own command interpreter/ shell like bash in unix/linux.
I need to execute basic commands like pipes and i/o.
Any help in this matter ?? (3 Replies)
Discussion started by: duma188
3 Replies
10. Red Hat
Hi,
I accidentally did this:
wadhwaso@nxsdgd01 deps]$sudo rpm -e --nodeps glibc-2.5-107.x86_64
error: %postun(glibc-2.5-107.x86_64) scriptlet failed, exit status 255
and since then I am not able to run any command on this server except 'cd'.
I always get the following error:
$ ls... (6 Replies)
Discussion started by: stunn3r
6 Replies
LUAC(1) General Commands Manual LUAC(1)
NAME
luac - Lua compiler
SYNOPSIS
luac [ options ] [ filenames ]
DESCRIPTION
luac is the Lua compiler. It translates programs written in the Lua programming language into binary files that can be later loaded and
executed.
The main advantages of precompiling chunks are: faster loading, protecting source code from accidental user changes, and off-line syntax
checking.
Pre-compiling does not imply faster execution because in Lua chunks are always compiled into bytecodes before being executed. luac simply
allows those bytecodes to be saved in a file for later execution.
Pre-compiled chunks are not necessarily smaller than the corresponding source. The main goal in pre-compiling is faster loading.
The binary files created by luac are portable only among architectures with the same word size and byte order.
luac produces a single output file containing the bytecodes for all source files given. By default, the output file is named luac.out, but
you can change this with the -o option.
In the command line, you can mix text files containing Lua source and binary files containing precompiled chunks. This is useful to com-
bine several precompiled chunks, even from different (but compatible) platforms, into a single precompiled chunk.
You can use '-' to indicate the standard input as a source file and '--' to signal the end of options (that is, all remaining arguments
will be treated as files even if they start with '-').
The internal format of the binary files produced by luac is likely to change when a new version of Lua is released. So, save the source
files of all Lua programs that you precompile.
OPTIONS
Options must be separate.
-l produce a listing of the compiled bytecode for Lua's virtual machine. Listing bytecodes is useful to learn about Lua's virtual
machine. If no files are given, then luac loads luac.out and lists its contents.
-o file
output to file, instead of the default luac.out. (You can use '-' for standard output, but not on platforms that open standard out-
put in text mode.) The output file may be a source file because all files are loaded before the output file is written. Be careful
not to overwrite precious files.
-p load files but do not generate any output file. Used mainly for syntax checking and for testing precompiled chunks: corrupted files
will probably generate errors when loaded. Lua always performs a thorough integrity test on precompiled chunks. Bytecode that
passes this test is completely safe, in the sense that it will not break the interpreter. However, there is no guarantee that such
code does anything sensible. (None can be given, because the halting problem is unsolvable.) If no files are given, then luac
loads luac.out and tests its contents. No messages are displayed if the file passes the integrity test.
-s strip debug information before writing the output file. This saves some space in very large chunks, but if errors occur when run-
ning a stripped chunk, then the error messages may not contain the full information they usually do. For instance, line numbers and
names of local variables are lost.
-v show version information.
FILES
luac.out default output file
SEE ALSO
lua(1)
http://www.lua.org/
DIAGNOSTICS
Error messages should be self explanatory.
AUTHORS
L. H. de Figueiredo, R. Ierusalimschy and W. Celes
$Date: 2006/01/06 16:03:34 $ LUAC(1)