Sponsored Content
Full Discussion: K&R C code edits
Homework and Emergencies Homework & Coursework Questions K&R C code edits Post 302562892 by theexitwound on Saturday 8th of October 2011 08:20:35 PM
Old 10-08-2011
But if the lines are split on the first -e expression, there should only be one function per line when the second -e expression is matched, shouldn't it?
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help with scripting mass file edits..

Hello, I am wanting to know a way to shell (ksh)script-edit a file by having a script that searches for a specific string, and then input lines of text in the file after that specific string. Please help, as I will be up all night if I can't figure this out. (16 Replies)
Discussion started by: LinuxRacr
16 Replies

2. Shell Programming and Scripting

Multiple edits to a bunch of html files

I'm trying to upgrade a whole bunch of pages on my site to a new design. I thought one way of doing it would be to enclose the content in special comment tags and then use some form of script to wrap the new html around it. Like this: <!-- content start --> <h1>Blah blah blah</h1> yada yada... (9 Replies)
Discussion started by: dheian
9 Replies

3. Shell Programming and Scripting

PHP read large string & split in multidimensional arrays & assign fieldnames & write into MYSQL

Hi, I hope the title does not scare people to look into this thread but it describes roughly what I'm trying to do. I need a solution in PHP. I'm a programming beginner, so it might be that the approach to solve this, might be easier to solve with an other approach of someone else, so if you... (0 Replies)
Discussion started by: lowmaster
0 Replies

4. UNIX for Dummies Questions & Answers

Compile & Run Java Code

The java program is a part of speech tagger -> The Stanford NLP (Natural Language Processing) Group The goal is to use this script as part of a webpage to tag parts of speech based on a user-inputted string. I have no idea what to do with the files - I'm a complete *nix noob. I tried running... (4 Replies)
Discussion started by: tguillea
4 Replies

5. UNIX for Dummies Questions & Answers

OpenLDAP DB_CONFIG edits, changes live? or do I need run something

So I am probably missing something , but when I made edits to my DB_CONFIG file to fix form db_lock issues, the changes are not propagating after a service restart. Anyone know if I need to run anything else, or are the changes live? (0 Replies)
Discussion started by: jcejka
0 Replies

6. Shell Programming and Scripting

Problem with call of Java Programm & return code handling & output to several streams.

Hello Everybody, thanks in advance for spending some time in my problem. My problem is this: I want to call a java-Programm out of my shell skript, check if die return code is right, and split the output to the normal output and into a file. The following code doesn't work right, because in... (2 Replies)
Discussion started by: danifunny
2 Replies

7. UNIX for Dummies Questions & Answers

multiple text edits inone pass

File_1 looks like: bunch of text Untitled Placemark bunch of text bunch of text Untitled Placemark bunch of text bunch of text Untitled Placemark bunch of text File_2 looks like: Title_001 Title_002 Title_003 First: I need to replace the 1st occurence of "Untitled Placemark"... (2 Replies)
Discussion started by: kenneth.mcbride
2 Replies

8. Shell Programming and Scripting

SFTP Shell Script Get & Delete && Upload & Delete

Hi All, Do you have any sample script, - auto get file from SFTP remote server and delete file in remove server after downloaded. - only download specify filename - auto upload file from local to SFTP remote server and delete local folder file after uploaded - only upload specify filename ... (3 Replies)
Discussion started by: weesiong
3 Replies
c89(1)							      General Commands Manual							    c89(1)

NAME
c89 - Standard C Compiler SYNOPSIS
c89 [-c] [-D name [=value]]... [-E] [-g] [-I directory]... [-L directory]... [-o outfile] [-O] [-s] [-U name]... file... STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: c89: XPG4, XPG4-UNIX Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
The following options are defined by the XPG4-UNIX standard. However, the compiler can also recognize the options defined in cc(1). Unlike cc(1), c89 includes the -std1 option by default (for ANSI C standards checking). To check for full compliance to XPG4-UNIX, you must also specify -D_XOPEN_SOURCE_EXTENDED. See standards(5) for more information. Suppress the loading phase of the compilation and force an object file to be produced. Produce symbol table information for full symbolic debugging and suppress optimizations that limit full symbolic debugging. Symbol types and stack-frame variables names are available. Global optimizations are not performed. Instruction scheduling does not span source line boundaries. Trap instructions are inserted to ensure that exceptions are reported on the source lines that caused them to be generated. Remove the symbol table and relocation bits to save space (this impairs the usefulness of the debuggers). This informa- tion can also be removed by strip(1). Name the final output file output. If this option is used, the file a.out is undisturbed. Define the name as if with a #define statement. If no definition is given, the name is defined as 1. Run only the C macro preprocessor on the files and send the result to the standard output device. Specifies that #include files whose names do not begin with / are always sought first in the directory of the file argument, then in directories specified in -I options, and finally in the standard directory, /usr/include. Adds dir to the list of directories that are searched for libraries. Directories specified with -L are searched before the standard directories. Enable global optimization, including code motion, strength reduction and test replacement, split lifetime analysis, and code scheduling. Remove any definition of name previously defined with the -D option. DESCRIPTION
Compiles source code in conformance with the XPG4-UNIX standard. The c89 command can process one or more of the following types of "file" arguments: Files whose names end with are assumed to be C source programs. They are compiled, and each object program is left in the file whose name consists of the last component of the source with sub- stituted for file is deleted only when a single source program is compiled and linked in a single step. Files whose names end with are assumed to be libraries of object files. These files are passed directly to the linker. Files whose names end with are assumed to be object files produced by a previous c89 command. These files are also passed directly to the linker. The c89 command can take other types of file arguments, although they are not part of the standard specification. See cc(1) for a descrip- tion of the other file types. When the compiler is invoked, it defines the following C preprocessor macros that identify the language of the input files and the environ- ments in which the code can run: __LANGUAGE_C__ __unix__ __osf__ __alpha _SYSTYPE_BSD LANGUAGE_ASSEMBLY __LANGUAGE_ASSEMBLY__ You can reference these macros in #ifdef statements to isolate code that applies to a particular language or environment. ERRORS
The diagnostics produced by c89 are intended to be self-explanatory. Occasional messages may be produced by the assembler or loader. EXAMPLES
Compiles helloworld.c and produces the executable file helloworld.c c89 -o helloworld helloworld.c Compiles helloworld.c and creates the object file helloworld.o. c89 -c helloworld.c Compiles a.c and b.c, producing a.o and b.o. The object files main.o, a.o, and b.o are then linked together, using the library /a/b/c/libQ.a to resolve any references in a.o, and /a/b/c/libp.a to resolve any references in b.o. The executable program is placed in the file a.out. Only one -L option is needed because libQ.a and libp.a reside in the same directory. c89 -L /a/b/c main.o a.c -l Q b.c -l p ENVIRONMENT VARIABLES
The following environment variables affect compiler operation: Provides a default value for locale variables that are not set. If any of these variables contains an invalid setting, the compiler behaves as if none were set. If set to a non-empty string, this variable over- rides values in all locale variables, including LANG. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte characters instead of multi-byte characters in arguments and input files). Determines the locale used for diagnostic messages. Determines the locale of message catalogs for the processing of LC_MESSAGES. Provides a pathname that overrides the default directory for temporary files, if any. For more information on these environment variables, see i18n_intro(5) and l10n_intro(5). FILES
Input file Object file Loaded output Compiler error messages in English Temporary Compiler configuration file (optional) C front end C macro preprocessor DEC C compiler Binary ucode and symbol table joiner Ucode loader Binary ucode and symbol table splitter Procedure inte- grator Optional global ucode optimizer Post-link optimizer Code generator Symbolic to binary assembly language translator Binary assembly language assembler and reorganizer Run-time startup Startup for profiling Standard library, see intro(3) Level 1 profiling library Standard directory for #include files Interface between prof and cord Procedure rearranger Binary-to-symbolic ucode translator Symbolic-to-binary ucode translator File produced for analysis by prof File produced for analysis by gprof SEE ALSO
Commands: as(1), cc(1), ld(1) Other: i18n_intro(5), l10n_intro(5), standards(5) Guides: ANSI X3.159-1989 B. W. Kernighan and D. M. Ritchie, The C Programming Language B. W. Kernighan, Programming in C -- a tutorial D. M. Ritchie, C Reference Manual Programmer's Guide Assembly Language Programmer's Guide Compaq C Language Reference Manual c89(1)
All times are GMT -4. The time now is 07:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy