CoDJumper.com

please if you have any info type back

Well. Lets start with the problems with your Pc first.

YOU CAPSLOCK KEY IS STUCK!

Now onto other problems.

Use a sensible title... such as
"What is a DC file".

Then in the subject field, that is where you describe your problem.

K, on to the problem in hand.

A DC file. What is this DC file associated with, why do you get the problem with this DC file? What has the DC file got to do with Call of Duty?

Etc.

Maybe if you were more descriptive and less anxious you might get an answer that would help.

dc-file - Standard extractable documentation

DESCRIPTION

This manual page describes the format of the standard extractable documentation that is required for all IA3 modules, i.e., procedures, subroutines, functions, Calibration files, SEDs, etc.
The documentation can be extracted by a general purpose file extractor xfile (see xfile.dc1 ) which is available in $UTL_SRC.

For xfile and CoCo to recognized such an extractable part in any file, the documentation must be surrounded by tags on a separate line.

The tag which defines the start of the extractable documentation part is defined as follows:


[flag]#> filename.ext


The optional flag can be any (zero, one or two) character(s) and will normally signify a comment, e.g., `#' for the Perl and Shell programming language, `C' for FORTRAN, `;' for IDL, etc.

The filename.ext will be used as the name of the output file. If this file already exist, it will be overwritten without warning.

The tag which defines the end of the extractable documentation part is defined as follows:


[flag]#<


The optional flag must be the same as for the starting tag.

All lines between these two tags must start with the flag . Lines that do not start with flag will simply be skipped and will not appear in the output. The flag itself will not be copied to the output file.

So far so good, extractable documentation is recognized by the tags. A few examples may clarify this. The following part is an example for the Perl programming language:


##> split_lines.dc5
#Identifier SplitLines
#
#Purpose Split large file into pieces
.
.
.
#History 0.1 25.09.95 ++rh Documentation and first implementation
##<


The next part is an example for the IDL programming language:


;#> split_lines.dc5
;Identifier SplitLines
;
;Purpose Split large file into pieces
.
.
.
;History 0.1 25.09.95 ++rh Documentation and first implementation
;#<


The IA3 programming standards also define the format of all extractable documentation. This format is described in section 4 of the IA3 Programmer Manual (ISO 94-48). This manual page only describes the most important items. For a full description, refer to the authoritative documentation.


Keywords are case insensitive and mandatory. If a keyword is not appropriate in the current context, fill in a few dashes `--' as input.

Inputs for a keyword must not start before column 16 and may not exceed column 80. For most keywords a multiline input is allowed, possibly separated by one or more blank lines.

Between successive keywords, there must be a blank line, which must of course contain the flag character.

There may not be a blank line before the first keyword and after the last keyword.

TAB characters will be automatically converted to 8 spaces.

There may be more than one extractable documentation part in a single file. All separate parts will automatically be extracted and written in the specified output files.

*You might find the answer in there*

Striker wrote:*You might find the answer in there*

Or die trying?

It's better then nothing at all

loOol ye. all that info came from my ed ! oh so u dont beleive me uh!

I'll use that post as a bedtimestory.....makes you fall asleep real quick

LOL!

If someone post something very big, i don't even bother reading it

I'll read it if it iterests me and this clearly doesn't.

Lol, that's what i meant.

hehe, you typed all of that out strider?

I doubt that

Ctr-C, Ctr-V

That's what I was thinking lol