home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
rtsi.com
/
2014.01.www.rtsi.com.tar
/
www.rtsi.com
/
OS9
/
OSK
/
EFFO
/
forum16.lzh
/
SOFTWARE
/
ASSEMBLER
/
DEMERGE
/
info_demerge
< prev
Wrap
Text File
|
1991-04-01
|
5KB
|
131 lines
$COMMENT
***********************************************************************
* This file is a so-called "Info" file describing a piece of *
* software in a standardized way using EFFO's "Info" file format. *
* The format provides all basic information about a program *
* in a well structured manner allowing automatic extraction *
* of important short-form data for databases and software lists *
* but including more detailed descriptions as well. *
* The structure is formed by a set of keywords dividing the *
* information into different paragraphs (see syntax description *
* below). *
* *
* Many programs distributed by EFFO will include such a file. *
* It will be called Info_xxxx, where xxxx is the program's name. *
* EFFO encourages all its members and all forum participants as *
* well as commercial suppliers of OS-9 and OS-9000 software to *
* use this format to describe their software. *
* An empty "form" for Info files called "Info_empty_form" will *
* be distributed with all EFFO disks and through the OS9-BBS. *
* *
* The syntax is quite simple: Each paragraph begins with a *
* "keyword line" which is a line with a $-Sign in the very first *
* column immediately followed by the keyword itself. The rest of *
* the line is reserved for short comments about the paragraph's *
* purpose. Some paragaphs are mandatory, and some are restricted *
* in size to ensure that reliable database entries can be *
* extracted automatically from the file. *
* All subseqent lines up to the next keyword line (or the *
* end-of-file) are forming the paragraph body, i.e the information *
* that belongs to the keyword. *
* The order in which the keywords appear in the text (if they *
* appear at all for optional paragraphs) is free with one *
* important exception: "$PROGRAM-NAME" always must be the first *
* keyword in the program description. This rule allows multiple *
* descriptions to be merged into a single text file without using *
* special delimiters in between. *
* Finally, "$COMMENT" paragraphs are provided to include *
* any information not related to a program description, like *
* this text. They can appear anywhere in the file, even before *
* the first "$PROGRAM-NAME". *
***********************************************************************
$COMMENT
This file is an empty form that can be used to create a "Info" file for
a program by inserting appropriate text between the keyword lines below.
This template lists all possible keywords. Altough it is recommended to
supply information for as many keywords as possible, all keyword lines
marked "optional" can be omitted from an info file. If you are not yet
familiar with the "Info" file concept, please have a look at existing
info files before filling in this form, in order to get an idea of what
sort of information we expect for the various keywords.
$PROGRAM-NAME demerge
$VERSION V0/Rev.0/Edt0
$PURPOSE De-merges a merged file to single module files
$SUMMARY usable to de-merge e.g. an OS9Boot to single files to replace
single modules.
$KEYWORDS Demerge, Modules
$PROJECT -
$STATUS final
$REFERENCES -
$HARDWARE no special
$SCREEN-INTERFACE none
$PREREQUISITES none
$HARDWARE-OPTIONS none
$OS-VERSION all (I hope)
$DOCUMENTATION none
$RUNTIME-FILES Input file - output files created with names of modules
contained in input file
$DOCUMENTATION-FILES none
$SOURCE-LANGUAGE Assembler
$SOURCE-AVAILABILITY Yes, Public
$SOURCE-FILES demerge.a
$SOURCE-PREREQUISITES standard
$COMPILATION r68 demerge.a -qo=[RELS/]demerge.r
l68 demerge.r -o=demerge -l=/dd/lib/sys.l
$AUTHOR-NAME W. Wittig
$AUTHOR-INFO Albrechtstr. 44, D-6100 Darmstadt
$AVAILABILITY Public
$CONDITIONS No military use - distribution only with this limitation note.
$COPYRIGHT W. Wittig - free - no military use
$DISTRIBUTOR EFFO
$HISTORY none
$EXPANSION none
$HOLDER
$INSTALLATION copy to your execution directory - then "demerge mergedfile"
$BUGS none I know
$RESTRICTIONS merged file may not exceed 64000 bytes in length
$DESCRIPTION
$EXPERIENCES
$NOTES Restriction above is due to reading whole merged file in memory. An
other way would be to read one module at a time into memory and writing it
to file.
$MISCELLANEOUS