UREAD(1)

πŸ“¦ version 0, in fedora 43, fedora 44

πŸ’– UREAD(1) β€” General Commands Manual πŸ’–

okay bestie, real talk: this page is filed under UREAD(1) but the star of the show is a lil program called ustrip. naming chaos? iconic. let's go πŸ¦‹


✨ NAME ✨

utrip β€” strips record length information from a Fortran unformatted file πŸ’…


🌸 SYNOPSIS 🌸

ustrip [ -x ] [ filename ]

πŸŽ€ DESCRIPTION πŸŽ€

so here's the vibe: ustrip reads in a file that was created with Fortran's unformatted IO, and it strips the record size flags that pad each record. why do we care?? because this is mainly of use for reading binary data into a C program. periodt. πŸ”₯

the -x option tells ustrip to byte swap the record flags, which lets you peek at big endian data on a little endian machine, and vis versa. (yes, "vis versa", that's what it says, we don't fix it, we respect it πŸ™ˆ) πŸ”„

and the file name? you may specify it on the command line. if you don't, the data gets read in from standard input and written out to standard output. streamy. ✨


⚠️ NOTE ⚠️

if you ever see this error message:

uread: data larger than file length
bestie that often means the file you're reading has the opposite byte "sex" to the platform uread is being run on 😭 try the -x flag and see if that's the case!! 🫢

πŸ‘€ SEE ALSO πŸ‘€


πŸ’œ AUTHOR πŸ’œ

S.E. Norris s.norris@auckland.ac.nz β€” thank you for your service, legend πŸ‘‘


and that's the whole page, bestie!! this was UREAD(1) from the General Commands Manual section, and yeah β€” the page is literally headed UREAD(1) at the bottom too, which is the whole source/version/date situation we got here: just the name, twice, no cap πŸ’€βœ¨ go forth and unpad those records, you absolute main character πŸŒˆπŸ’–

πŸ“¦ where this page comes from