home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!walker
- From: walker@twix.unx.sas.com (Doug Walker)
- Subject: Re: AmigaDOS library functions and ANSI-C programming
- Originator: walker@twix.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <C0C2wK.G1s@unx.sas.com>
- Date: Mon, 4 Jan 1993 14:29:07 GMT
- References: <1992Dec29.221144.26405@urbana.mcd.mot.com>
- Nntp-Posting-Host: twix.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 31
-
-
- In article <1992Dec29.221144.26405@urbana.mcd.mot.com>, qbarnes@urbana.mcd.mot.com (Quentin Barnes) writes:
- |> I ran across a widespread problem with the AmigaDOS specific
- |> prototypes/libraries with writing ANSI-C code. AmigaDOS
- |> functions which take pointers to objects when the objects
- |> aren't modified are not marked as "const". For example,
- |> the ANSI-C code:
- |> const char *s = "mylib";
- |> OpenLibrary(s,0L);
- ...
- |> Has the problem been covered before? Is there plans in the
- |> works to support ANSI-C/C++ clean AmigaDOS library calls?
-
- |> Quentin Barnes
-
- I hope that Commodore addresses these issues soon. Fortunately,
- if and when they do SAS/C is prepared to deal with it. There
- is a command-line option to tell the compiler to treat all
- quoted strings as "const char *" instead of "char *", and all
- the code is present to deal with const correctly. We can't
- turn the option on by default because of this exact problem.
-
- --
- *****
- =*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
- *|. o.| || 1200/2400/9600 Dual
- | o |// For all you do, this bug's for you!
- ======
- usenet: walker@unx.sas.com bix: djwalker
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-