Sponsored Content
Full Discussion: Documenting files with sed
Top Forums Shell Programming and Scripting Documenting files with sed Post 303000442 by f77hack on Wednesday 12th of July 2017 09:03:08 AM
Old 07-12-2017
Quote:
Originally Posted by RudiC
Where would you locate the "first left parenthesis"?
yes sorry, my mistake, right parenthesis.
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Documenting a Shell Script

I've been working on a very long shell script that's becoming a mini-application. It is my first script, and continues to grow each week, becoming more and more complex. I've been asked to document my script, beginning with basic information and then detailing any information about its... (1 Reply)
Discussion started by: yongho
1 Replies

2. UNIX for Dummies Questions & Answers

Any easy way of documenting cron entries?

I've been asked to do a high level summary of the cron jobs which run against a number of systems (to understand the potential scope for rewriting some of our core systems)...and was wondering how people have done this in the past. I've got approx 400 cron entries to go through. I will have... (2 Replies)
Discussion started by: GavP
2 Replies

3. Programming

Documenting code

I am programming using C++ and am wondering how to comment my project. For example, when I declare a class I created a header with some description, then have the declaration stage, which I don't comment. Then when I define the actual functions I will put details about it, what it does,... (2 Replies)
Discussion started by: kristinu
2 Replies

4. Shell Programming and Scripting

Script Help -- documenting specific users that log into server

Hello All, I am trying trying to write a shell script that will do a couple things: 1.) Identify any username that logs into the server. 2.) When the user logs out, send them an email detailing their log in/out times, duration logged in, and what processes they ran. Basically,... (3 Replies)
Discussion started by: SecureScript
3 Replies

5. Web Development

Documenting Installation Problem with vue-beautiful-chat

REF: https://github.com/mattmezza/vue-beautiful-chat $ git clone https://github.com/mattmezza/vue-beautiful-chat.git Cloning into 'vue-beautiful-chat'... remote: Enumerating objects: 534, done. remote: Total 534 (delta 0), reused 0 (delta 0), pack-reused 534 Receiving objects: 100%... (2 Replies)
Discussion started by: Neo
2 Replies
ANSI2KNR(1)						      General Commands Manual						       ANSI2KNR(1)

NAME
ansi2knr - convert ANSI C to Kernighan & Ritchie C SYNOPSIS
ansi2knr [--filename filename] [input_file [output_file]] DESCRIPTION
--filename provides the file name for the #line directive in the output, overriding input_file (if present). If no input_file is supplied, input is read from stdin. If no output_file is supplied, output goes to stdout. There are no error messages. ansi2knr recognizes function definitions by seeing a non-keyword identifier at the left margin, followed by a left parenthesis, with a right parenthesis as the last character on the line, and with a left brace as the first token on the following line (ignoring possible intervening comments). It will recognize a multi-line header provided that no intervening line ends with a left or right brace or a semi- colon. These algorithms ignore whitespace and comments, except that the function name must be the first thing on the line. ansi2knr also recognizes adjacent string literals and concatenates them. The following constructs will confuse it: - Any other construct that starts at the left margin and follows the above syntax (such as a macro or function call). - Some macros that tinker with the syntax of the function header. - String literals whose concatenation requires rewriting their contents; e.g. "ab " "07c" is concatenated to "ab 07c", which is not correct. The --varargs switch is obsolete, and is recognized only for backwards compatibility. The present version of ansi2knr will always attempt to convert a ... argument to va_alist and va_dcl. AUTHOR
L. Peter Deutsch <ghost@aladdin.com> wrote the original ansi2knr and continues to maintain the current version; most of the code in the current version is his work. ansi2knr also includes contributions by Francois Pinard <pinard@iro.umontreal.ca>, Jim Avera <jima@net- com.com>, and Paul Eggert <eggert@twinsun.com>. 8 March 2000 ANSI2KNR(1)
All times are GMT -4. The time now is 07:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy