This web site is a front end to a
repository
of Awk code.
The site, and the code, is maintained
by the international awk community (which includes you)
so there are many ways you can contribute:
Test the page by placing it on a publicly readable site, then see if it renders ok.
Email the url of that page to mail@awk.info. Do NOT send the page.
When writing a page, please follow these guidelines:
Do not use <hr> tags: these are reserved for dividing pages in a multi-page view.
Use only one <h1> tag at the top of page. Everything else should
<h2> or below.
Try to avoid using tricky CSS/HTML styling tricks. Vanilla HMTL is best.
The page you write will end up being rendered as the
middle pane of this site (around 550 pixels wide). So don't
write wide pages.
If you include code samples, note that our CSS wraps pre-formatted
code if it gets too wide. For example, at the time
of this writing, the following pre-formatted texts
gets ugly after about 75 characters:
In the language of this site, a function file is a 100% standalone file containing one or more
functions with no dependancies on other files.
Note that if your function file depends on other files, then it becomes a package (see below).
Functions are stored in a file caled myfunc.awk.
Add a Package
In the language of this site, a package is a file that depends on other files
(and the other files may depend on yet others, recursively).
Following a recent discussion in comp.lang.awk, we say that these dependancies are commented with
#use file.awk
where file.awk is some
file (e.g. a file in the current directory).
Note that :
file.awk will be loaded before the file containing the reference to #use file.awk.
