NetNews Usenet Archive 1993 #1/NN_1993_1.iso/spool/comp/sys/amiga/programm/18491

Text File | 1993-01-11 | 3.8 KB | 86 lines

Newsgroups: comp.sys.amiga.programmer
Path: sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!walker
From: [e-mail] (Doug Walker)
Subject: Re: ETA for SAS 6.2?
Originator: [e-mail]
Sender: [e-mail] (Noter of Newsworthy Events)
Message-ID: <[e-mail]>
Date: Mon, 11 Jan 1993 14:16:19 GMT
References: <[e-mail]> <[e-mail]> <[e-mail]>
Nntp-Posting-Host: twix.unx.sas.com
Organization: SAS Institute Inc.
Lines: 72


In article <[e-mail]>, [e-mail] (Jarno Tapio Rajahalme) writes:
|> I'd have few suggestions to the 6.2 (or 6.3 if too late for the 6.2):

Thanks for the suggestions, but 6.2 is frozen - these will be filed
for possible future use.

|> The function of __saveds in the function definition is same as having
|> geta4() call as first in the function body. It would be nice if
|> __saveds were effective only if near data addressing is used OR there
|> were a preprocessor symbol that would be defined in near (or far) data
|> addressing mode depending the compiler options.

Even if a given module does not use near data, we still preserve
register A4.  This is because it's possible that a function CALLED BY
the current function uses near data.  For the same reason, __saveds
and geta4() must work whether or not the function so declared uses
near data or not.  (And, I might add, an explicit request from the
user to restore A4 should definately NOT be ignored.)

If you know for a fact that your program doesn't use any near data
at all, use the DATA=FARONLY option, which will free up register
A4 for use as an additional register variable.

|> When debugging a library with cpr the highlighting of breakpoint lines
|> got spread (along with the breakpoint number in the beginning of the
|> line) to almost every line when scrolling. Sorry I can't be more
|> specific on this.

I don't understand this report at all.  Please clarify.

|> There is some confusion about the number of underscores before the
|> CXBRK(): On-line documentation (sc_lib.guide) has one underscore
|> [_CXBRK()], while paper documentation (User's Guide, V1, at index) has
|> two underscores and the Library Reference doesn't even mention the
|> function.

It's always possible to use OML on the link libraries to determine
what the library is actually referring to.  In this case, you need
one underscore since CXBRK starts with a capital letter.  Compiler-
provided non-ANSI routines must start with two underscores or one
underscore and a capital letter, according to the ANSI standard,
so the general rule is to add underscores until the name comes into
compliance.  (Note, however, that routines that are not defined in
an ANSI header file or used automagically by the compiler will not
have any underscores, the theory being that ANSI-compliant programs
won't be including non-ANSI header files anyway.)

|> On smake documentation (page 279, on the bottom) there is a typo: The
|> first line of the table starts with S@ when it should be $@ :-)

Touche'  8^)

|> PS: Which is the preferred media for suggestions like this (news,
|> main, emits)?

EMITS is the best, since it's guaranteed we won't miss it.  News
as well as EMITS is helpful, since it may generate discussion which
will flesh out suggestions and give us a better idea of what people
want.

|> | Address: Jarno Rajahalme            | EMail:                              |

--
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: [phone] =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ======
usenet: [e-mail]                            bix: djwalker
Any opinions expressed are mine, not those of SAS Institute, Inc.