03-09-2017
It is difficult to diagnose problems in code we haven't seen. If you show us the original code and the modifications you have made to it, we would have a MUCH better chance of helping you.
10 More Discussions You Might Find Interesting
1. Programming
I am having strange warnings from gcc compiler, which I don't think should come while cmpiling.
Can anyone help? The warnings are:
- warning: implicit declaration of function 'bzero'
- warning: implicit declaration of function 'inet_addr'
The code is as below:
int main(int argc, char... (2 Replies)
Discussion started by: Ahsan
2 Replies
2. Shell Programming and Scripting
Is it possible to pass a variable name, as a parameter to a function, so it can be created within this function ?
Something like this:
func_uppercase abcdefgh var_name
where the 1st parameter is the string I want to convert and the 2nd is the desired variable name...
$2=`echo "$1" |... (2 Replies)
Discussion started by: 435 Gavea
2 Replies
3. BSD
I am running Open BSD 3.8 (3.5 upgrade) on a Pent Pro. 200, 64 Megs Ram, Nvedia Vanta TNT 16 Megs, Realtech 8139 Nic. When running ifconfig -a I get this error back. I've run searches on google no deal. I can get Stack overflow or psync, but not both. So I would really like to know how to fix it. ... (0 Replies)
Discussion started by: jmcpreach
0 Replies
4. Linux
Hi
I compiled a hello world program on two different 64-bit Linux machines, named quimby and node0331. When I compile on quimby and run on node0331 I get a "Floating exception (core dumped)" error. But if I do it in reverse, things work fine.
Here's my compilation on quimby:
$ uname -a... (3 Replies)
Discussion started by: same1290
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have the following statement which parses a string for me and prints it out:
l_comp="dc000.runksh.test.ksh|
$g_sql/dc0000.runksh_test.sql|new.dat|control.ctl"
echo $l_comp | awk -F"|" '{ for ( i = 1; i <= NF; i++) { print $i; } } '
Rather then printing the data, I would like to... (5 Replies)
Discussion started by: CAGIRL
5 Replies
6. Programming
I have a class called Parsing with the following function. I want to create a wrapper for it, so that I call it using GetReal rather than GetFloat.
Bit confused on how to do this.
class Parsing {
private:
int Length; //
int Ptr; ... (3 Replies)
Discussion started by: kristinu
3 Replies
7. Programming
I have put some yellow color codes and works well.
I call the funstion using
print_usage(stderr, 0);
I would like to know if there is any way, to store the ansi color codes in variables and then call them inside fprintf.
Or have a format followed by the strings I want to output.
... (5 Replies)
Discussion started by: kristinu
5 Replies
8. Solaris
Hello experts,
This issue has kept me busy all day long. It started off with openssl compilation which was giving linking error with following message:
/usr/local/bin/ld: target elf32-sparc not found
collect2: ld returned 1 exit status
I tried every step possible thing that I could think... (2 Replies)
Discussion started by: d_shanke
2 Replies
9. Programming
I hope it's okay to post this here. I'm working on Windows computer but using the Unix-like environment MSYS2 (https://sourceforge.net/projects/msys2).
My problem is that I can't get the compiler to find headers located in /usr/local/include. I am trying to compile libpng which wants the header... (1 Reply)
Discussion started by: AntumDeluge
1 Replies
10. Shell Programming and Scripting
Hi,
If I declare a function inside another function, it overwrites any previously declared function with the same name. This is NOT what I want.
Example:
#!/bin/bash
_test() { echo test; }
_myf() {
# I'm using the same name as the other function.
_test() { echo local test; }... (8 Replies)
Discussion started by: chebarbudo
8 Replies
LEARN ABOUT DEBIAN
luac50
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 latter loaded and
executed.
The main advantages of precompiling chunks are: faster loading, protecting source code from 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.
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.
The binary files created by luac are portable to all architectures with the same word size. This means that binary files created on a
32-bit platform (such as Intel) can be read without change in another 32-bit platform (such as Sparc), even if the byte order (``endian-
ness'') is different. On the other hand, binary files created on a 16-bit platform cannot be read in a 32-bit platform, nor vice-versa.
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. The output file may be a source file because all files are loaded before the out-
put 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 these chunks, then the error messages may not contain the full information they usually do (line numbers and names of locals
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 (lua@tecgraf.puc-rio.br)
2002/12/13 11:45:12 LUAC(1)