Documenting files with sed Post: 303000442

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...

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...

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,...

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,...

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%...

LEARN ABOUT BSD

lorder

LORDER(1)						      General Commands Manual							 LORDER(1)

NAME

       lorder - find ordering relation for an object library

SYNOPSIS

       lorder file ...

DESCRIPTION

       The input is one or more object or library archive (see ar(1)) files.  The standard output is a list of pairs of object file names, meaning
       that the first file of the pair refers to external identifiers defined in the second.  The output may be processed by tsort(1) to  find	an
       ordering of a library suitable for one-pass access by ld(1).

       This brash one-liner intends to build a new library from existing `.o' files.

	      ar cr library `lorder *.o | tsort`

       The need for lorder may be vitiated by use of ranlib(1), which converts an ordered archive into a randomly accessed library.

FILES

       *symref, *symdef
       nm(1), sed(1), sort(1), join(1)

SEE ALSO

       tsort(1), ld(1), ar(1), ranlib(1)

BUGS

       The names of object files, in and out of libraries, must end with `.o'; nonsense results otherwise.

4th Berkeley Distribution					  April 29, 1985							 LORDER(1)