Sponsored Content
Full Discussion: compiling troubles
Top Forums Programming compiling troubles Post 7289 by PxT on Monday 24th of September 2001 11:30:00 AM
Old 09-24-2001
Re: compiling troubles

Quote:
Originally posted by token


#define DEBUG(fmt) if(traceflag) { \
fprintf(stderr, fmt, arg1); \
Don't include a slash at the end of the line. Your define should be somthing like:

#define DEBUG(fmt) if(traceflag) { \
fprintf(stderr, fmt, arg1);
/* rest of your program goes here */
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

NetBSD Troubles

HI, I just installed NetBSD i386 v. latest. I am having a few problems: For some reason X just won't start!? Another is I can't access My CDROM or Floppy. Thanks in advance! (3 Replies)
Discussion started by: vertigo
3 Replies

2. Programming

Troubles with HPUX

Hello I created an application in c language for HP-UX operative system,and it runs on a 32 bits PARISC processor. My problem is that I have to run this same application but now in a 64 bits Parisc processor. But I am not able to compile the application with the 64 bit server, and I only could use... (1 Reply)
Discussion started by: masterboy6666
1 Replies

3. UNIX for Dummies Questions & Answers

Password Troubles

I'm very new to UNIX (I just started working with Terminal 2 days ago) and I don't know the system very well. I'm having trouble whenever I am asked for a password. I simply... can't type. I press keys on the keyboard but no characters appear on the screen. For example, when I log onto... (5 Replies)
Discussion started by: alexmiller
5 Replies

4. HP-UX

cron troubles

I have a cronjob that I need to run everyday and it needs to have todays date inputed, here is what I have, but is not working as expected.......... 23 02 * * * cd /path;./RequestSummaryReport.sh $(date +%Y-%m-%d) the output from mail gives me............. Date: Fri, 8 Feb 2008 02:12:07... (4 Replies)
Discussion started by: theninja
4 Replies

5. Shell Programming and Scripting

if-statement troubles

I try to compare the day and month of someones birthday with the day and month of today, so my little bash script can send a mail to the person that has its birthday that day. The first line of the file birthdays looks like this: firstname,lastname,01/01/1990,.... The variable birthday's... (4 Replies)
Discussion started by: doc.arne
4 Replies

6. Shell Programming and Scripting

Encoding troubles

Hello All I have a set of files, each one containing some lines that follows that regex: regex='disabled\,.*\,\".*\"'and here is what file says about each files: file <random file> <random file> ASCII text, with CRLF line terminatorsSo, as an example, here is what a file ("Daffy Duck - The... (3 Replies)
Discussion started by: tukuyomi
3 Replies

7. UNIX for Dummies Questions & Answers

Cron troubles

I am aware this question has been answered time and again. I feel I have tried everything I have seen on the net and really need help to get this working. Same old story. Shell script, working from command but not from cron. I need my script to take values from a .properties file. Tried... (2 Replies)
Discussion started by: airalpha
2 Replies

8. Shell Programming and Scripting

for loop troubles

What I have here is a pretty textbook recursive function. Its purpose right now is simply to display all folders that don't contain folders. It works fine in all instances I can think of... except one. If there is a folder with a space in its name, the thing goes Kablooie. AFAIK the problem comes... (5 Replies)
Discussion started by: divisionbyzero
5 Replies

9. Shell Programming and Scripting

awk and tr troubles

I am trying to make all the fields containing lower case letters upper case and the third field of a file display ** instead. I have this: awk '{printf "%s %s ** %d %d\n", $1, $2, $4, $5}' database.txt | tr '' '' < database.txt And that only changes it to upper case, other... (4 Replies)
Discussion started by: Bungkai
4 Replies

10. UNIX for Advanced & Expert Users

Troubles with OpenSSH

Hi, I am trying to login from one AIX server to another without using a password, a basic configuration, however it doesn't seem to work. All things are in place. I have both a public and private key in the ~/.ssh folder and also have an "authorized_keys" file on the target-server containing... (5 Replies)
Discussion started by: Hille
5 Replies
epp_dodger(3erl)					     Erlang Module Definition						  epp_dodger(3erl)

NAME
epp_dodger - epp_dodger - bypasses the Erlang preprocessor. DESCRIPTION
epp_dodger - bypasses the Erlang preprocessor. This module tokenises and parses most Erlang source code without expanding preprocessor directives and macro applications, as long as these are syntactically "well-behaved". Because the normal parse trees of the erl_parse module cannot represent these things (normally, they are expanded by the Erlang preprocessor epp(3erl) before the parser sees them), an extended syntax tree is created, using the erl_syntax mod- ule. DATA TYPES
errorinfo() = {ErrorLine::integer(), Module::atom(), Descriptor::term()} : This is a so-called Erlang I/O ErrorInfo structure; see the io(3erl) module for details. EXPORTS
parse(Dev::IODevice) -> {ok, Forms} | {error, errorinfo()} Equivalent to parse(IODevice, 1) . parse(Dev::IODevice, L::StartLine) -> {ok, Forms} | {error, errorinfo()} Types IODevice = pid() StartLine = integer() Forms = [syntaxTree() (see module erl_syntax)] Equivalent to parse(IODevice, StartLine, []) . See also: parse/1 . parse(Dev::IODevice, L0::StartLine, Options) -> {ok, Forms} | {error, errorinfo()} Types IODevice = pid() StartLine = integer() Options = [term()] Forms = [syntaxTree() (see module erl_syntax)] Reads and parses program text from an I/O stream. Characters are read from IODevice until end-of-file; apart from this, the behav- iour is the same as for parse_file/2 . StartLine is the initial line number, which should be a positive integer. See also: parse/2 , parse_file/2 , parse_form/2 , quick_parse/3 . parse_file(File) -> {ok, Forms} | {error, errorinfo()} Types File = filename() (see module file) Forms = [syntaxTree() (see module erl_syntax)] Equivalent to parse_file(File, []) . parse_file(File, Options) -> {ok, Forms} | {error, errorinfo()} Types File = filename() (see module file) Options = [term()] Forms = [syntaxTree() (see module erl_syntax)] Reads and parses a file. If successful, {ok, Forms} is returned, where Forms is a list of abstract syntax trees representing the "program forms" of the file (cf. erl_syntax:is_form/1 ). Otherwise, {error, errorinfo()} is returned, typically if the file could not be opened. Note that parse errors show up as error markers in the returned list of forms; they do not cause this function to fail or return {error, errorinfo()} . Options: {no_fail, boolean()} : If true , this makes epp_dodger replace any program forms that could not be parsed with nodes of type text (see erl_syn- tax:text/1 ), representing the raw token sequence of the form, instead of reporting a parse error. The default value is false . {clever, boolean()} : If set to true , this makes epp_dodger try to repair the source code as it seems fit, in certain cases where parsing would oth- erwise fail. Currently, it inserts ++ -operators between string literals and macros where it looks like concatenation was intended. The default value is false . See also: parse/2 , quick_parse_file/1 , erl_syntax:is_form/1 . parse_form(Dev::IODevice, L0::StartLine) -> {ok, Form, LineNo} | {eof, LineNo} | {error, errorinfo(), LineNo} Types IODevice = pid() StartLine = integer() Form = syntaxTree() (see module erl_syntax) LineNo = integer() Equivalent to parse_form(IODevice, StartLine, []) . See also: quick_parse_form/2 . parse_form(Dev::IODevice, L0::StartLine, Options) -> {ok, Form, LineNo} | {eof, LineNo} | {error, errorinfo(), LineNo} Types IODevice = pid() StartLine = integer() Options = [term()] Form = syntaxTree() (see module erl_syntax) LineNo = integer() Reads and parses a single program form from an I/O stream. Characters are read from IODevice until an end-of-form marker is found (a period character followed by whitespace), or until end-of-file; apart from this, the behaviour is similar to that of parse/3 , except that the return values also contain the final line number given that StartLine is the initial line number, and that {eof, LineNo} may be returned. See also: parse/3 , parse_form/2 , quick_parse_form/3 . quick_parse(Dev::IODevice) -> {ok, Forms} | {error, errorinfo()} Equivalent to quick_parse(IODevice, 1) . quick_parse(Dev::IODevice, L::StartLine) -> {ok, Forms} | {error, errorinfo()} Types IODevice = pid() StartLine = integer() Forms = [syntaxTree() (see module erl_syntax)] Equivalent to quick_parse(IODevice, StartLine, []) . See also: quick_parse/1 . quick_parse(Dev::IODevice, L0::StartLine, Options) -> {ok, Forms} | {error, errorinfo()} Types IODevice = pid() StartLine = integer() Options = [term()] Forms = [syntaxTree() (see module erl_syntax)] Similar to parse/3 , but does a more quick-and-dirty processing of the code. See quick_parse_file/2 for details. See also: parse/3 , quick_parse/2 , quick_parse_file/2 , quick_parse_form/2 . quick_parse_file(File) -> {ok, Forms} | {error, errorinfo()} Types File = filename() (see module file) Forms = [syntaxTree() (see module erl_syntax)] Equivalent to quick_parse_file(File, []) . quick_parse_file(File, Options) -> {ok, Forms} | {error, errorinfo()} Types File = filename() (see module file) Options = [term()] Forms = [syntaxTree() (see module erl_syntax)] Similar to parse_file/2 , but does a more quick-and-dirty processing of the code. Macro definitions and other preprocessor direc- tives are discarded, and all macro calls are replaced with atoms. This is useful when only the main structure of the code is of interest, and not the details. Furthermore, the quick-parse method can usually handle more strange cases than the normal, more exact parsing. Options: see parse_file/2 . Note however that for quick_parse_file/2 , the option no_fail is true by default. See also: parse_file/2 , quick_parse/2 . quick_parse_form(Dev::IODevice, L0::StartLine) -> {ok, Form, LineNo} | {eof, LineNo} | {error, errorinfo(), LineNo} Types IODevice = pid() StartLine = integer() Form = syntaxTree() (see module erl_syntax) | none LineNo = integer() Equivalent to quick_parse_form(IODevice, StartLine, []) . See also: parse_form/2 . quick_parse_form(Dev::IODevice, L0::StartLine, Options) -> {ok, Form, LineNo} | {eof, LineNo} | {error, errorinfo(), LineNo} Types IODevice = pid() StartLine = integer() Options = [term()] Form = syntaxTree() (see module erl_syntax) LineNo = integer() Similar to parse_form/3 , but does a more quick-and-dirty processing of the code. See quick_parse_file/2 for details. See also: parse/3 , parse_form/3 , quick_parse_form/2 . tokens_to_string(Tokens::[term()]) -> string() Generates a string corresponding to the given token sequence. The string can be re-tokenized to yield the same token list again. AUTHORS
Richard Carlsson <richardc@it.uu.se > syntax_tools 1.6.7 epp_dodger(3erl)
All times are GMT -4. The time now is 03:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy