Selective file copy: Difference between revisions

Show how file processing as known from PL/I or COBOL can be implemented in the

language of your choice.

 

=={{header|ALGOL 68}}==

{{works with|ALGOL 68G|Any - tested with release 2.8.3.win32}}

Using formatted transput to process similar files to the COBOL sample.

MODE OUTPUTRECORD = STRUCT( STRING field a, INT field c, STRING field x );

 

close( output file );

close( input file )

 

Input file:

Output and formatting is done using printf().

 

 

BEGIN {

print "# Done."

}

 

{{out}}

levels. In this example only levels 01, and 05 are used.

 

01 ws-input-record.

:INPUT-RECORD:

 

01 ws-input-record.

05 field-a pic x(5).

05 field-c pic s9(5).

05 field-d pic x(5).

 

And finally, the example selective-copy.cob

*> Tectonics:

*> cobc -xj selective-copy.cob

.

 

 

The output file has no newlines, so normal '''cat''' type commands are not of

 

=={{header|Fortran}}==

TYPE PLACE

INTEGER N

IS.LATLONG = HERE.LATLONG !Piecemeal, as no common structure was defined.

WRITE (6,*) IS !Reveal the result.

This produces a file in a standard format. All output starts with a space in column one (in case this output were to be sent to a lineprinter, for which that would be the carriage control character), and begins the block of output with a special line that gives the name of the NAMELIST prefixed with an ampersand, and ends it with a slash. Each line starts with the name of a variable followed by an equals, then comes its value in the same style as would be used in free-form output, using a field large enough for its largest value. Some extra spaces are supplied before the = according to name length to improve readability. The whole line looks much as if it were an assignment statement in Fortran. There is special provision for listing the values of arrays which normally are shown one after another in the standard order. A run of equal values will be shown with a repetition count as in ... ,6*T, ... for six "true" values in a row, alas not using an @ symbol. CHARACTER variables will be shown with all their characters and even if they are all blank, they will not be shown as "" though that is acceptable for input. There is a default record length of 133 (again for lineprinters) and a variable may require multiple lines; CHARACTER variables split across lines include the content of the first character of the next line, but otherwise the line break is after a comma. Structure names alas use % instead of a full stop, but a full stop may be accepted as input. Before F90, such data aggregates were not available, so only ordinary variables could be named.

<pre>

 

Output:<pre> Mt. Cook trig. (-41.29980,174.7763)</pre>

 

=={{header|Go}}==

JSON is popular these days for structured data and Go has support for this kind of selective copy in the JSON reader. The reader also supports custom conversions on fields. The common idiom for record construction and field initialization is shown.

 

import (

}

}

{{out|o1.json}}

<pre>

{"A":"AAAAA","C":"5","X":"XXXXX"}

</pre>

 

=={{header|Java}}==

With a little help from my friens

import java.io.FileWriter;

import java.io.File;

return;

}

 

=={{header|NetRexx}}==

with a little help from a friend

-- nrc -keepasjava -savelog copys

options replace format comments java crossref symbols nobinary

ex.printStackTrace()

end

 

=={{header|ooRexx}}==

infile ="in.txt"

outfile="out.txt"

expose instream outstream

instream~close

{{out}}

<pre>AA 01XXXXX

AAAA 03XXXXX

AAAAA04XXXXX

 

=={{header|PL/I}}==

copys: Proc Options(Main);

Dcl 1 s1 unal,

eoj:

End;

{{out}}

<pre>AA 01XXXXX

AAAAA04XXXXX

AAAAA05XXXXX</pre>

 

=={{header|REXX}}==

{{trans|PL/I}}

out='out.txt'; 'erase' out

Do While lines(in)>0

Call lineout in

Call lineout out

{{out}}

Using the test file produced by PL/I.

AAAAA04XXXXX

AAAAA05XXXXX</pre>