Re: Binary files vs Portablity vs Ada

[nahaj@u.cc.utah.edu (John Halleck)]

Larry Kilgallen (kilgallen@eisner.decus.org) wrote:
: [...] nahaj@u.cc.utah.edu (John Halleck) writes:

: > [...]

: >   It is not hard to do something that just grabs bytes from a file
: >   until done, but that assumes the file is some multiple of eight
: >   bits long, and that all data for the file is in the bytes returned.
: >   On machines like the Sperry 1100 series, the native word size is
: >   36 bits (Usually chopped into four nine-bit bytes for Text use)
: >   And the file is "control word -> image"  instead of "embeded
: >   control."
: > 
: >   Can this be done portabily?  (I suspect not, but I'm not an Ada
: >   expert.)  I have something that seems to work for PC's, Mac's, 
                                      *****
: >   and Unix boxes, but it bugs me that I don't know how to do it in
: >   any general way.

: Does your Mac version do the resource fork or just the data fork ?

  (:  Only Data  :)  The project was only to show a co-worker about
  some of the ease of doing things portably in Ada.  It was not
  for a production product...  

: > [... good examples of other portablitity issues ommitted ...]

: So hardware data size is not your only issue.

  True enough.

  For the purpose of getting the bits for a hash there are other
  issues which I would expect the Language Designers not to have
  addressed.

  For example, on many OS's, files can have unallocated regions
  within the body of the file.  How does one handle that for a
  Hash?  (Or even doing direct IO?)  There are ugly issues everywhere.


  This discussion seems to be drifting from the "Do it in Ada" question
  to "Boy the world is ugly portablity wise."

  I'm more than willing to continue this thread in private email with all
  interested parties.

: Larry Kilgallen