Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 263,235 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to Waldek Hebisch    |
|    Re: Binutils    |
|    05 Sep 25 19:24:53    |
   
   From: arne@vajhoej.dk   
      
   On 9/5/2025 7:12 PM, Waldek Hebisch wrote:   
   > Arne Vajhøj wrote:   
   >> On 9/5/2025 1:40 PM, Waldek Hebisch wrote:   
   >>> I would expect that having records   
   >>> of length 3 and then setting length to 2 would also truncate   
   >>> data in the records.   
   >>   
   >> $ set file/attr does not change the content of the file only the   
   >> file header meta data.   
   >>   
   >> AAA   
   >> BBB   
   >> CCC   
   >>   
   >> 41 41 41 00   
   >> 42 42 42 00   
   >> 43 43 43 00   
   >>   
   >> does not become:   
   >>   
   >> AA   
   >> BB   
   >> CC   
   >>   
   >> 41 41   
   >> 42 42   
   >> 43 43   
   >>   
   >> but:   
   >>   
   >> AA   
   >> A*   
   >> BB   
   >> B*   
   >> CC   
   >> C*   
   >>   
   >> 41 41   
   >> 41 00   
   >> 42 42   
   >> 42 00   
   >> 43 43   
   >> 43 00   
   >   
   > I am not sure how you are getting result above. I created a   
   > simple variable length file and I get:   
   >   
   > $ set FILE/ATTR=LRL:2 VTST.TXT   
   > $ type VTST.TXT   
   > a   
   > bcd   
   > $ set FILE/ATTR=LRL:1 VTST.TXT   
   > $ type VTST.TXT   
   > a   
   > bcd   
   >   
   > That is 'type' is getting right records regardless of my LRL setting.   
   > Naive program could truncate records. Slightly better one   
   > could get records in pieces of size corresponding to   
   > LRL (possibly creating more record on output than is present in   
   > the input). But truncating with odd LRL setting and reading   
   > record padding bytes with even LRL setting look like a bug   
   > (which may remain unfixed forever due to requirement for   
   > bug compatibility).   
      
   Sorry. I am still messing around in RFM FIX.   
      
   It can be deduced from the hex, but I should have been explicit.   
      
   I create the FIX file simply by creating a VAR in EVE and do a:   
      
   $ convert/fdl="record;format fixed;size 3" var-file fix-file   
      
   I think VAR is way less sensitive to MRS/LRL than FIX.   
      
   VAR use the length in the record prefix. FIX has to take the length   
   from the header.   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca