HDTenEightyP/NetNews huggingface dataset:
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: A3000 for Programming
Originator: jamie@cdevil.unx.sas.com
Date: Mon, 12 Oct 1992 14:44:10 GMT
Organization: SAS Institute Inc.


In article <iJBgsB1w165w@lakes.trenton.sc.us>, mr_scary@lakes.trenton.sc.us (Chris Hurley) writes:
>jamie@cdevil.unx.sas.com (James Cooper) writes:
>
>> Also, if the errors are in your program, you can just link with catch.o
>> in place of c.o, to catch the GURUs before they happen.
>
>I assume catch.o is new to 6.0?  If this works, it is a god send.  Does
>this feature require an MMU?  (I will be upgrading to 6.0 regardless of
>whether I get a 3000 or not...

Nope.  The alternative catch.o startup has been there since about V5.00
(I'm not sure anymore...).

It just hasn't been documented very well in the past, and you *had* to
do the Blink step separately until V5.10 (when the new -t switch was
added to LC).

No, it doesn't require an MMU.  It patches your process' tc_TrapData and
tc_TrapCode vectors (*only* if not running under a debugger!), and then
writes an IFF PGTB file to the current directory.  A separate program,
named TB is supplied with the compiler to interpret this file.

However, if the GURU occurs because you passed bad data to a system
routine (or otherwise occurs outside your program space), it will *not*
be caught.  Unfortunately, there is no system-approved way to catch this
type of GURU (although several products, such as GOMF, have tried...).

-- 
---------------
Jim Cooper
(jamie@unx.sas.com)                             bix: jcooper

Any opinions expressed herein are mine (Mine, all mine!  Ha, ha, ha!),
and not necessarily those of my employer.
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: C++ and Amiga shared libs (was: Re:  Obj-C vs. C++)
Originator: walker@twix.unx.sas.com
Date: Fri, 16 Oct 1992 14:01:57 GMT
Organization: SAS Institute Inc.


In article <Bw64pC.DpJ@well.sf.ca.us>, comeau@csanta.attmail.com (Greg Comeau) writes:
|> >You should be able to create a shared library in C++ assuming all 
|> >of the following are true (Greg may be able to help on some of 
|> >these):

|> >   *) Comeau C++ provides near-data-model libraries (libraries compiled
|> >      without the DATA=FAR (6.0) or -b0 (5.10) option.

Hmm, I did some checking and apparently this is a sticking point
right now.  Greg has said that he has plans to ship libraries
compiled with DATA=NEAR, but apparently the current product does
not have them.

You can still create the library, but you'll get a lot of linker
warnings (feel free to ignore them) and you should take steps in
your code to make sure that only ONE opener is allowed to use
your library, then your library gets flushed.  This should allow
you to debug the library so you'll be ready when the new C++
libraries become available.

You'll also probably need to call geta4() instead of using
the __saveds keyword, since I believe Comeau C++ doesn't
handle the __saveds keyword.  Look up geta4() in your
Library Reference documentation.

-- 
  *****
=*|_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.

Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re:  INPUT DEVICE problems...
Originator: walker@twix.unx.sas.com
Date: Tue, 13 Oct 1992 12:34:51 GMT
Organization: SAS Institute Inc.


In article <1992Oct12.172809.1172@gn.ecn.purdue.edu>, seifert@gn.ecn.purdue.edu (Michael S. Seifert) writes:
|> Below is the code for a very simple input device handler, which just flashes
|> the display when the letter 't' is pressed. No problem here... However,
|> when I change the DisplayBeep to something like Tpressed=TRUE; the 
|> program comes crashing down.  
|> 
|> Can anyone tell me what I've done wrong?  I've seen at least ten different
|> input device sources, but none of them do anything so simple as to just
|> read the keyboard and set a flag.  I'd welcome any simple source mailed to
|> me to accomplish this, especially all C source (this isnt going to be
|> the greatest multitasking program...).    Thanks, mike.

When you install an input handler, it gets called under the
input.device's task, not yours.  Therefore, your near data 
register (A4) is not set up to point to your near data.  You 
should declare your input handler routine with the __saveds
keyword, which will generate code to load register A4 at
entry to your function.  You should also be careful to compile
with no stack checking or stack extension, and do not use cres.o
to make your program resident (since with cres.o you can't use
a 32-bit reference to load A4).

struct InputEvent *__asm __saveds
inputhandlercode(register __a0 struct InputEvent *keyevent)
{
   ...
}

-- 
  *****
=*|_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.
Organization: Middle East Technical University - Computer Center
Date: Thursday, 8 Oct 1992 11:44:03 TUR
From: <E63256@TRMETU.BITNET>
Newsgroups: comp.sys.amiga.programmer
Subject:    System BOB background saving/restoring

I use system routines (1.3) to draw bobs. I want to ask that whether the
system restores the whole bob sized rectangle or only the destroyed background
    I mean if for example the bob's overlay is all zeros then the drawing
of that bob won't destroy any background. So infact no restoration will
be required for this special case.

Shortly I want to learn that if the system restores the background through the
OVERLAY of the bob or by a direct copy.

Also If any ROM differances exist in this context I'll be glad to know.


     Thanks in advance.                -Erhan OZTOP-
Newsgroups: comp.sys.amiga.programmer
From: tron@uni-paderborn.de (Matthias Scheler)
Subject: Bug in SAS/C 6.0
Keywords: SAS/C
Organization: Uni-GH Paderborn
Date: Tue, 13 Oct 1992 22:01:09 GMT


	Hi,

after recompiling a program written with SAS/C 6.0 I got lots of crashes.
After two hours of debugging I found the problem:
A call to wbench.library/AddAppIcon via one of the new tagcalls trashed the
a4-register. Anyone got the same problem and maybe found a solution ?
I took the old pragma-files without "#tagcall" which stopped the crashes.
-- 
Matthias Scheler                                         tron@uni-paderborn.de
University of Paderborn (Germany)
From: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Random No.s in AmigaDOS ??
Date: 12 Oct 92 17:17:30 GMT
Reply-To: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Organization: Commodore Germany

In article <1992Oct12.093044.3346@lugb.latrobe.edu.au> csccm@luxury.latrobe.edu.au (Chris Miles!!) writes:
>
>Can anyone tell me how you make random numbers in AmigaDOS ??
>I want to write a small script file that does different things randomly,
>so how do I get this random number??!

Well, incidentally we were just talking about how to further enhance the next
generation of AmigaDOS manuals, and one idea was to provide more examples
for AmigaDOS scripts. One of my proposals (of which I can't swear whether
it will make it anytime into that manual) is the following. It just takes
the Seconds value of the Date output. If you don't call this too fast in
series, you can get at least an "idea" of a random number (:-).
Cited:

The next script is a demonstration how you can extract an info from
the middle of an output line and process it, all with the means of
script commands.

Example 12, name RND:
      ; generate a random number
      ; take the result of Date as input
      date  >ram:zuf1
      ; generate a second script (don't care here for multitasking and <$$>)
      echo  >ram:zuf2 ".key z1,z2,z3"
      ; take only last 2 characters of 3rd argument (z3)
      echo >>ram:zuf2 "echo >env:zuf3 *"<z3>*" len=2"
      ; generate a third script, first line not yet completed!
      echo  >ram:zuf4 "execute ram:zuf2 " noline
      ; complete the line and the script
      ; the result of Date is presented as arguments z1,z2,z3 to zuf2,
      ; and thus can be separated into z1=weekday, z2=date, z3=time
      join   ram:zuf4 ram:zuf1 as ram:zuf5
      ; execute the script, gives the seconds value in zuf3
      execute ram:zuf5
      ; do a little arithmetics (divide by 2) to the seconds value
      eval <env:zuf3 >nil: value2=2 op=/ to=env:zuf6 ?
      ; show a random value between 0 and 29
      type env:zuf6
      ; clean up
      delete ram:zuf1 ram:zuf2 env:zuf3 ram:zuf4 ram:zuf5 env:zuf6 quiet

Usage: RND
When you use this as a macro to call from (or include into) another
script, leave off the last two command lines and work with the
environment variable zuf6. Don't forget to clean up later! You also
may change (or delete) the Eval command that can scale your value.

(Remark: The variable name "zuf" stems for the german word "Zufall"
for random event.)

-- 
Best regards, Dr. Peter Kittel  // E-Mail to \\  Only my personal opinions...
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.graphics
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: InterViews?
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 8 Oct 1992 02:49:20 GMT

In article <1992Sep30.185317.16747@murdoch.acc.Virginia.EDU> tmb@faraday.clas.Virginia.EDU (Thomas M. Breeden) writes:
>Is anybody aware of any effort to port the InterViews GUI environment
>(from Stanford/SGI/HP etc) to AmigaDOS?

I have not heard of anybody who has done this yet.  If somebody else
has I would be interested in hearing about it.

>It's all C++. Has anybody done a BIG project with Comeau C++?

We have people from all sorts of life and places using Comeau C++,
especially with our UNIX ports.  Why do you ask?

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
From: kevint@hpsad.sad.hp.com (Kevin Taddeucci)
Date: Fri, 9 Oct 1992 16:46:21 GMT
Subject: HELP: Software Failure #81000005
Organization: HP Signal Analysis Division - Rohnert Park, CA
Newsgroups: comp.sys.amiga.programmer

 This may not belong in this group but I figure nobody knows more about 
 software failures than programmers, so here goes.
 

 While trying to use Polyfonts in VideoTitler3D version 1.5, I get a 
 software failure #81000005. According to the 2.04 includes and autodocs 
 manual this number indicates a "Corrupt Memory List Detected in FreeMem.
 
 I have been talking to Oxxi and they said they have never seen this 
 problem and can not re-create it. 

 My configuration is a 16MHz A3000 with 6Megs of RAM. 2 CHIP / 4 FAST.
  
 My question are: 
 
 Could this failure be caused by a bad memory chip? 
 
 If so, does anyone know of a shareware/PD memory test program?
 
 Any other ideas on what the problem could be?
 

                           THANKS IN ADVANCE!
       ----------------------------- ------------------------------------
      | Kevin J. Taddeucci          | e-mail: kevint@hpsad.sad.hp.com    |
      | Hewlett Packard Firmware QA | HPDesk: Kevin TADDEUCCI /HP5300/A0 |
      | Telnet: 794-4192            | HP Mailstop: 2LR-N                 | 
       ----------------------------- ------------------------------------

 

Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: InterViews?
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 8 Oct 1992 03:14:40 GMT

In article <1992Oct3.114345.9877@ccsnews.ccs.mt.nec.co.jp> sugai@spls38.ccs.mt.nec.co.jp (Masaru Sugai) writes:
>In article <1328@lorentz.sbi.com> peter@aristotle.sbi.com (Peter Murray) writes:
>>
>>InterViews is x-window based.  It's design is supposed to make it easy to
>>move from x-window to some other windowing system, but I can imagin that this
>>would be a VERY large effort to do so....
>
>I have to agree with you on the toughness of porting

I suspect it wouldn't be the simplest thing in the world either.
Might actually be impossible but I don't pretend to be a multi-platform
GUI guru, so alternatively it might be possible.

>Another problem is a C++ environment which is compliant to AT&T C++.
>Comeuer's(sp?) C++ seems to be good in this respect, and they might
>have tested it, as InterViews is considered as a good test case for
>C++ compilers.

It's 'Comeau' ;-).  Anyway yes, not only are we compliant with AT&T C++, but
Comeau C++ is literally AT&T C++ (we are licensees).  Re testing with
Interviews, obviously not under AmigaDOS, however under UNIX it works like
a charm as do most 3rd party libraries with Comeau C++.

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: How to boot from Kickstart in WB_2.x/Devs ?
Originator: jamie@cdevil.unx.sas.com
Date: Mon, 12 Oct 1992 15:01:01 GMT
Organization: SAS Institute Inc.


In article <1992Oct12.103233.3783@samba.oit.unc.edu>, Uwe.Illig@bbs.oit.unc.edu (Uwe Illig) writes:
>
>I installed a new Kickstart file in my WB_2.x:Devs drawer and thought that
>my Amiga 3000 would use this file version of Kickstart instead of the ROMs,
>because in the readme it was described this way.
>But after a reboot I always get the ROM version.
>With SetCpu I can load the Kickstart file and it works, but I want the system
>to load the kickstart version in the Devs drawer directly.
>
>Do I have forgotten something?

Do you have the release 2.04 ROMs?  V37.175 was the release Kickstart
version.

If you are a developer, contact Commodore about this.  If you are not a
developer, you are a pirate, and should know better than to post in an
open conference...

If you have the older, original (V36.???) ROMs, placing a new Kickstart
file in WB_2.x:Devs is all you should need to do.

Again, if you are a developer, contact Commodore if this is not working.

If you are just a customer, the lastest Kickstart you should have is the
2.04 (V37.175) version, which your dealer should be able to replace for
you if it is defective.  If you have anything later, you are a pirate...

-- 
---------------
Jim Cooper
(jamie@unx.sas.com)                             bix: jcooper

Any opinions expressed herein are mine (Mine, all mine!  Ha, ha, ha!),
and not necessarily those of my employer.
From: bell@ecs.umass.edu
Newsgroups: comp.sys.amiga.programmer
Subject: Stringgadgets and 2.0
Date: 14 Oct 92 20:40:15 GMT
Article-I.D.: ecs.18755.2adc85b0


	I'm trying to create string gadgets to provide a more proper Amiga
interface for my programs.  I'm using GadtoolsV1.4 to create a window with a
couple string gadgets in it.  Although I don't understand all the functions
they compile fine and run properly.  However, I want to find out what people
type into them.  How do I go about finding out what somebody typed in them?
	Thank you for any and all help in this matter.

			Shane L. Bell
			bell@ecs.umass.edu
Newsgroups: comp.sys.amiga.programmer
From: mctaylor@mta.ca (Michael C. Taylor)
Subject: ToolKit for Amiga/XWindows GUI
Reply-To: mctaylor@mta.ca
Organization: Mount Allison U, Sackville, N.B. Canada 
Date: Wed, 7 Oct 1992 22:17:47 GMT

Is there a toolkit which can be used to create a common GUI for an amiga
application and a X-Windows application? I want to create some programs on
my amiga with a GUI which I might wish to port since they could end up to be
processor intense. I'd rather not rewrite the GUI, as much as possible.
Any ideas?
From: walker@twix.unx.sas.com (Doug Walker)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: SAS/C 6.0 in Europe?
Date: 8 Oct 92 13:15:49 GMT
Organization: SAS Institute Inc.
Originator: walker@twix.unx.sas.com


In article <1992Oct7.191936.13918@polaris.utu.fi>, sutela@polaris.utu.fi (Kari Sutela) writes:
|> 
|> Has anyone in Europe received an upgrade notice for SAS/C from the SAS
|> Heidelberg office?  According to an article by Doug Walker they should
|> have been sent about two weeks ago.  Should I begin worrying :-)?
|> 
|> -- 
|> Kari Sutela	sutela@utu.fi

I have not been told whether they have sent the upgrade letter.
I assume not.  But there is no need to wait for the letter; you
can go ahead and order from them.  Here's their contact info one
more time:

SAS Institute GmbH
PO Box 10 53 07
Neuenheimer Landstrasse, 28-30
6900 Heidelberg 1

Telephone (49)6221-4150
Fax       (49)6221-474850

-- 
  *****
=*|_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.
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: OpenScreenTags()...I'm confused
Date: 12 Oct 92 22:22:09 GMT
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore-Amiga, Inc.  West Chester, PA.

In article <1992Oct11.185205.3501@crash> rtillery@crash.cts.com (Rick Tillery) writes:
>What _IS_ the deal with OpenScreenTags()?  I've just begun using 2.0
>only routines, and this is confusing the heck out of me:
>
>There is a prototype for OpenScreenTagList() and OpenScreenTags().
>There is a pragma for OpenScreenTagList() but NOT for OpenScreenTags().

OpenScreenTagList() is the actual function in the ROM.  Its prototype is:

struct Screen *OpenScreenTagList( struct NewScreen *, struct TagItem * );

The second parameter is a pointer to a taglist.  You might use this function
in this manner:

    struct NewScreen myns =
    {
	/* place your init here */
    };

    struct TagItem mytags[] =
    {
	SA_PubName, "MyPublic",	/* example tag, makes screen public */
	...			/* more tags can go here */
	TAG_DONE, 0,
    };

    ...

    if ( myscreen = OpenScreenTagList( &myns, mytags ) )
    {
	...
    }

OpenScreenTags() is a "varags conversion stub".  It extracts a pointer
to a bunch of tags on the stack and calls OSTagList().   You can code it
for yourself in this manner:

struct Screen *OpenScreenTags( struct NewScreen *ns, ULONG tag1, ... )
{
    return( OpenScreenTagList( ns, (struct TagItem *) &tag1 ) );
}

This allows you to write:

    struct NewScreen myns =
    {
	/* place your init here */
    };

    ...

    if ( myscreen = OpenScreenTags( &myns,
	SA_PubName, "MyPublic",
	...				/* more tags can go here */
	TAG_DONE ) )
    {
	...
    }

The latter form is more convenient from C.  The compiler vendor
should be providing prototypes for both forms of a function.  SAS/C 5
and Aztec 5 provide pragmas only for the "TagList" form, since converting
the stack arguments requires different processing.  SAS/6 supports
"pragma tagcall" which allows all tag-based functions to be invoked
via "pragmas".  The "amiga.lib" library contains the code for
OpenScreenTags(), and other similar functions, but these stubs assume
that your library bases are in far global variables.  If your
compiler doesn't support pragma tagcall or its equivalent, and you're
not using "large data", then you'll have to code up your own stubs
as shown, I think.

>Rick Tillery

     Peter
--
Peter Cherna, User Interface Development Group, Commodore-Amiga, Inc.
{uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"I believe it's bad luck to be superstitious."
From: dylan@cs.washington.edu (Dylan McNamee)
Newsgroups: comp.sys.amiga.programmer
Subject: AREXX parsing madness  -- will it ever be fixed?
Summary: where did AREXX learn to parse???
Date: 13 Oct 92 15:08:12 GMT
Organization: Computer Science & Engineering, U. of Washington, Seattle


I recently completed my first AREXX macro, a paren matching program for
QED.  It works now, although quite slowly.  I had a bear of a time getting
it to pass AREXX, though, and for the goofiest reasons:

"Everyone" knows an AREXX program has to have a comment as its first line...

The parentheses for a function call _have_ to abut the function name, as in:
  a_function(an_arg)
but
  a_function (an_arg) croaks...and the error message isn't informative...

"end else do" on the same line also croaks, without an intelligible error
message.

And so on.  I would think that since this is ostensibly the "replacement" for
Amiga Basic, that CBM would be taking pains to make the language a bit more
forgiving...but the above problems are absolutely inexcusable.  White space
should be white space should be white space, and error messages should be
at least _hints_ as to what the problem is.

To end this tirade with a question, though:  If AREXX lacks a function,
is it reasonably efficient to write the function in "C", make it resident, 
and call it from AREXX?  I've found that functions written in AREXX, especially
ones that iterate through strings character at a time, are painfully slow.

 _|   | _  _
(_](_)|(_l| )  dylan@cs.washington.edu
    /
From: jac@moonshine.llnl.gov (James A. Crotinger)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Comeau C++
Date: 14 Oct 92 06:20:04 GMT
Organization: Magnetic Fusion Energy - LLNL

Lee_Robert_Willis@cup.portal.com writes:
> Hey Greg, why not include a name de-mangler utility with Comeau C++?

  Er, there is one. Check out "comofilt". Unfortunately, I don't know
if there is a man page for it in the manual. But if you just type
"comofilt" and then enter data to stdin, it converts the mangled names
into unmangled ones.

  Jim
--
-------------------------------------------------/\--------------------------
James A. Crotinger     Lawrence Livermore N'Lab // \ The above views are mine
jac@moonshine.llnl.gov P.O. Box 808;  L-630 \\ //---\  and are not neces-
(510) 422-0259         Livermore CA  94550   \\/Amiga\  sarily those of LLNL.