[Info-vax] Looking into C-include files on VMS

[Joerg Schilling]

In article <4cb86890-817a-4c07-8be1-c35b6b5842b8 at j19g2000yqk.googlegroups.com>,
Steven Schweda  <sms.antinode at gmail.com> wrote:

>   I've been trying for (what seems like) a (very) long time,
>with limited success, to get him to adopt some VMS-specific
>changes in various cdrtools programs related to process
>priorities (where VMS and POSIX differ), scanning every device
>on every SCSI adapter looking for optical-writing drives, and
>(my absolute favorite) "fwrite(buf, 1, len, f)" versus
>"fwrite(buf, len, 1, f)" (where one creates "len" one-byte
>records on VMS, while the other creates one "len"-byte record,
>and it doesn't matter on UNIX), so I have some idea how easy
>it is to get the changes I'd like into this package.  (See the
>"vms_notes.txt" file for the details.)  So, I wouldn't advise
>starting a fight over the merits of "smake".

I try to limit the amount of work for a port, this is why I
do more than just looking at a single point. If I change things, I do 
so with all my software in mind as all my software is based on the same
portability framework where every piece of code is reused.

>
>   No guarantees, of course, but a DCL procedure to extract C
>header files may be found at:
>
>      http://antinode.info/ftp/misc/cheader.com

This worked.

-- 
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de		(uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily