HDTenEightyP/NetNews huggingface dataset:
From: visconti@gecko.cis.ohio-state.edu (Mark Visconti)
Newsgroups: comp.sys.amiga.programmer
Subject: SAS C question
Date: 16 Oct 92 15:22:15 GMT
Article-I.D.: cis.1992Oct16.152215.5046
Organization: The Ohio State University Dept. of Computer and Info. Science


    I recently upgraded to SASC6.0 and have a question.  I've been RTFMs
(and reading and reading...), but haven't found an answer.

   I have several source files in a directory that I am compiling and linking
using the Build icon.  I've set up the options that I "think" are appropriate.
I'm getting undefined function linker warnings at link time (prompts for
stub routines).  The functions that the linker is complaining about are
in c routines in the directory and have been compiled successfully.  There
are several routines that the linker can not find.  The one thing these
routines have in common is that they are never directly called.  They are
called via a function pointer.   Is the linker throwing these out in an earlier
pass ? If so, is there a specific way I need to declare these routines ?

Thanks,
Mark
------------------------------------
visconti@cis.ohio-state.edu
Newsgroups: comp.sys.amiga.programmer
From: greendog@insti.physics.sunysb.edu (Michael D. Fischer)
Subject: Trying to scroll!
Organization: Institute for Theoretical Physics, SUNY at Stony Brook.
Date: Fri, 9 Oct 1992 16:09:56 GMT

I've got a C program that does some graphics, and I need a region to
scroll smoothly.  I set up a VERTB interrupt server using the C code
on p. 526 of the 2.0 Libraries RKM, and the ASM code on p. 527.

That worked fine (just a counter).  When I changed the ASM code to do
my scroll strange things happen.  The scrolling DOES work, smootly, for
about 3-4 seconds, and then the computer reboots.  Am I doing this totally
stupidly, or am I close; does anyone know what's wrong?  (using SAS/C 6.0)

        INCLUDE "include:exec/types.i"
        INCLUDE "include:hardware/custom.i"
        INCLUDE "include:hardware/intbits.i"

        XDEF    _VertBServer
        XREF    _LVOScrollRaster
        XREF    _LVOWaitBlit
        XREF    _GfxBase
        XREF    _rp
                                        * A1 = is_Data (rp) from C prog
        section code

_VertBServer
        movem.l d2-d7/a2-a4,-(sp)       * save registers

        movea.l _GfxBase,a6             * GfxBase
        jsr     _LVOWaitBlit(a6)        * wait for blitter to finish

                                        * rp is in a1 already
        move.l  #2,d0                   * dx
        move.l  #0,d1                   * dy
        move.l  #8,d2                   * xmin
        move.l  #13,d3                  * ymin
        move.l  #700,d4                 * xmax
        move.l  #100,d5                 * ymax
        jsr     _LVOScrollRaster(a6)    * do the scroll

        moveq.l #0,d0                   * set Z flag for other vb-servers

        movem.l (sp)+,d2-d7/a2-a4       * restore registers
        rts                             * return to exec

        end

--
-------------------------------------------------------------------------
- Michael D. Fischer - greendog@max.physics.sunysb.edu - (516) 632-7966 -
- System Manager - Institute for Theoretical Physics - SUNY Stony Brook -
-------------------------------------------------------------------------
- These things take time...  But this time, I know...          - Thomas -
-  That the beauty of a dream...  Is you don't let it go...    - Dolby  -
-------------------------------------------------------------------------
-- 
-------------------------------------------------------------------------
- Michael D. Fischer - greendog@max.physics.sunysb.edu - (516) 632-7966 -
- System Manager - Institute for Theoretical Physics - SUNY Stony Brook -
-------------------------------------------------------------------------
Newsgroups: comp.sys.amiga.programmer
From: Hans Ridder <ridder@zso.dec.com>
Subject: Re: Case-sensitive menu-shortcuts, any?
Originator: ridder@zowie.zso.dec.com
Organization: Digital Equipment Corporation - DECwest Engineering
Date: Sat, 10 Oct 1992 21:53:59 GMT

In article <1992Oct5.152607.23405@samba.oit.unc.edu> Todd_Lewis@unc.edu (Todd M. Lewis) writes:
>Your problem is to make your program as useable as possible.  What you
>should do is:
>* use raw-key codes (converted through the console.device)
>  to map menu keys to functions,
>* use the style-guide suggestions if at all possible,
>* make short-cuts only for those other menu items that are
>  completely unambiguous and don't conflict with the style guide, and
>* (this is the biggie) make ALL your menu items short-cut-able, and
>  make ALL your short-cuts user-configurable.

Hmmm.  I'm not sure I agree with the last one.  Doing that leads to all
sorts of really non-mnemonic short-cuts.  If I can't remember a short
cut, what good is it?  Also, doing this *along* with the previous
suggestions seems almost impossible....

>Todd M. Lewis / Todd_Lewis@unc.edu / utoddl@guitar.oit.unc.edu

-hans
-- 
  Hans-Gabriel Ridder				Digital DECwest Engineering
  ridder@rust.zso.dec.com			Bellevue, Washington, USA
  {pacbell,pyramid,uunet}!rust.zso.dec.com!ridder
From: jaker@csugrad.cs.vt.edu (Jake Rose)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: AmigaGuide
Date: 9 Oct 92 15:33:37 GMT
Organization: Virginia Tech Computer Science Dept, Blacksburg, VA

Steve.Nordquist@mtask.omahug.org (Steve Nordquist) writes:

>> ...AmigaGuide is part of 3.0!
> 
>(groan) OOooo.  So therefore there are >no< database programs that read .guide
>files but the True One (AmigaGuide in 3.0?)   Is there no interim measure?

Yes, there is an AmigaGuide reader with SAS/C 6.  There is also a public domain
reader that tends to die for one reason or another (on 2.04 machines at least)
on Fish Disk 739.  It's called "Hyper".
-- 

Wulf                    |Two men look out through the same bars.
jaker@csugrad.cs.vt.edu |One sees mud, and one the stars.

-- 

Wulf                    |Two men look out through the same bars.
jaker@csugrad.cs.vt.edu |One sees mud, and one the stars.
From: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: How to reset the ....... Amiga 3000?
Date: 11 Oct 92 16:04:19 GMT
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA


simons@peti.GUN.de (Peter Simons) writes:
>
>                                  Hi wizards !
>
>I have the following problem: I wrote a patch, that fixes  the  ColdRebot()-
>Bug under FASTROM. My resetroutine simply disables the caches  and  the  MMU
>before jumping to ColdReboot(). BUT: This doesn't work on the original A3000
>where the Kickstart is always loaded with  the  MMU,  because  no  ROMs  are
>available.

If you had read the docs, you will have notices that if you have a V36 or
better ROM, you should call a function called ColdReboot()...

Also, some FastROM tools (including the current one by Commodore) do not
correctly SetFunction this vector (ColdReboot) to do the needed un-FastROM
such that it continues to work.  Now, in general this is not much of an
issue, but it can be a pain...

I have a program I use to reset all of my machines...  It watches for
this special file to show up from the network (a new kickstart :-) and
then calls ColdReboot().  Works fine on all of the machines I use...

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///                     When people are free to do as they         |
| \XX/                      please, they usually imitate each other.   |
\----------------------------------------------------------------------/
From: ps296au@sdcc4.ucsd.edu (Steven Cobb)
Newsgroups: comp.sys.amiga.programmer
Subject: VBLANK Examples wanted.
Date: 8 Oct 92 22:53:53 GMT
Organization: University of California, San Diego

Does anybody know of some examples of vertical blank ISR's that 
are downloadable or on a fish disc?  I'm looking to do something
like color cycling and animation on a screen and time criticle
device triggering using the parallel port.

Is there any trick I should know about if I wish to JSR to a C (SAS
5.10) routine?  

Thanks in advance,
-- 
  \________/\      ______________________    __________________________________
Steven Cobb  \    /   scobb@ucsd.edu     \__/                Graduate School:
              \  /                                           It's not a job...
         UCSD  \/ ision Lab                                  It's an indenture.
Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re:  Comeau C++
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 15 Oct 1992 14:59:58 GMT

In article <1992Oct15.083706.5925@tpl68k0.tplrd.tpl.oz.au> paulg@tplrd.tpl.oz.au (Paul Gittings) writes:
>
>In article <Bw25nK.DLK@well.sf.ca.us>, comeau@csanta.attmail.com (Greg Comeau) 
>>... embedded systems even though we do not have a [target] C++ compiler
>
>Just to back Greg up on this, the company I work for (but don't speak for)
>is currently evaluating C++ for use in one of our embedded systems.  Nobody
>makes a C++ compiler for our target so we got a copy of Comeau C++ (runs on
>a SPARCStation), the output of which can be fed into our K&R C cross-compiler. 
>We are also considering using it on another project (again an embeded system)
>which currently uses G++ cross-compiling from a SPARCStation to a 68030
>based system. Comeau C++ doesn't have the bugs/problems that G++ has and
>it follows the current C++ standard (cfront) where as G++ doesn't.

Thanks for your words on this.  I wish more customers would speak up
as some consider my statements to be too biased.

>I'm
>not knocking G++/GCC/GNU/FSF etc, it will improve over time just as Comeau
>C++ has (and I hope will).

We will ;-)  In fact, as you should have been infromed at the time of your
purchases: Comeau C++ 3.0.1 is now starting to "hit the streets" as a free
upgrade/

>   Another thing to think about is the fact that G++ 
>is resource hungry (ie, it likes lots and lots of RAM). I have 5MB in my
>Amiga at home and I can't compile what I consider to be a simple C++
>program (opens a screen, couple of windows) due to running out of memory.
>So, if you plan on using G++ (2.2.2) expect to run into problems due to 
>incompatabilites with the current version of cfront 3.1 (?) ( I have heard
>of problems with G++ implementation of Templates and statics), and to have 
>to pay for extra RAM if you have 5MB or less.

I'm not knocking it either but issues like this are one part of the
reality of using it, just like some of the realities that Comeau C++ has.

- 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
From: wille@june.cs.washington.edu (Robert Wille)
Subject: Huffman encoding code wanted
Organization: University of Washington Computer Science
Date: Fri, 9 Oct 92 18:26:53 GMT

I'm looking for some code to do Huffman encoding.  Nothing special, just
something I can give a couple of buffers to and it will compress one into
the other.  It needs to be C code as it needs to be ported to another
platform.  If anyone has something like this, I'd appreciate it very
much.  Thanks in advance!

-- 
Robert

There is evidence that the brain is like a computer.  If that's true, 
then there really aren't any stupid people.  Just people running DOS.
Newsgroups: comp.sys.amiga.programmer
From: "robert buonincontro" <robert.buonincontro@canrem.com>
Subject: compiler errors
Reply-To: "robert buonincontro" <robert.buonincontro@canrem.com>
Organization: Canada Remote Systems
Distribution: comp
Date: 11 Oct 92 12:09:03 EST


   I have recently been using Lattice 6.0, and have found a compiler
error that I haven't encountered before.  Acutally, its a warning.
Specifically:

100: No prototype declared for function xxxx.

    I have fixed my functions to avoid the warning, by declaring them as
void, ie:  void func(void);
           void func
           {  ...... }

    What I can't seem to fix are the similar warnings being given about
intuitions functions.  Namely, OpenScreen(), OpenWindow(), Delay(),
Wait(), CloseWindow()...etc...

     I've looked this up to the best of my ability, and can't seem to
find the correct library to include.  Naturally, I include
intuition/intuition.h, otherwise these functions wouldn't work at all,
but I still get the warning.  I removed the warning for the printf(),
sprintf(), and other string functions by including <stdio.h>,
<string.h>.

        Does anyone know which library to include ??

        Robert Buonincontro
--
Canada Remote Systems  - Toronto, Ontario
World's Largest PCBOARD System - 416-629-7000/629-7044
Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re:  Comeau C++ class libraries
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Tue, 13 Oct 1992 11:39:40 GMT

>What sorts of "pre-rolled" classes are included with the Comeau C++
>package?  Is it mostly the standard container classes?  Are there any
>Amiga GUI-specific classes?

The Comeau C++ runtime library comes with the iostreams library,
and some compiler helper functions (like operator new()'').
We have tested many 3rd party libraries in the past and most work
(I say "most" not in that some libraries don't work but in that there
may be some that we have not yet tested or in that we have not heard
any feedback on).

Amiga classes have been a constant catch-22.  When we originally released
Comeau C++ for the Amiga, said was in our plans.  However, we were quickly
convinced that 3rd parties would do this.  Many did inform of this, but
apparently were not as sincere as we thought they would be.  Having said
this we are aware of two groups still involved however they have not yet
released anything.  This issue needs to be seriously reconsidered if
they are still light years away.

- 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
From: Todd_Lewis@unc.edu (Todd M. Lewis)
Subject: Re:  Multithreaded code using CreateTask()
Organization: UNC Office of Information Technology
Date: Thu, 15 Oct 1992 14:18:13 GMT

In article <dej.01r9@qpoint.ocunix.on.ca> dej@qpoint.ocunix.on.ca (David Jones)  
writes:
>In article <1992Oct5.151328.22908@samba.oit.unc.edu> Todd_Lewis@unc.edu (Todd  
M. Lewis) writes:
>>[Libraries may act differently]based on who called [OpenLibrary()]
>> (i.e. the result of FindTask(0)). Probably bad
>>design, granted, but such a beast could be made. 
>
>Well, if it's bad design then the IEEE math libraries are a piece of
>cr*p.  Seriously, C= has documented that such restrictions can exist,
>and it's up to us to follow them.

Hardly a piece of cr*p, they are pretty good from what I hear from
people who know about such things.  There is this qwerky little wart on
them though, as they (I think) change some things in you Task
structure when you open them up.  Sub-tasks must open them again to be
able to use them.  Seriously, there are libraries that work this way
and had better be documented as such.  Lots of "standard" libraries
(graphics, intuition and workbench for example) have not had such
restrictions in the past and will break a good number of extant
programs if that changes in the future.  New libraries would do well to
avoid this sort of restriction as well.  The nature of a library may be
such that such side effects on the opener is the most prudent way to go. 
I just don't believe this is usually (maybe ever) the case. 
OpenLibrary() is spec'd as returning a pointer to a library.  It isn't
good design to slip side effects into well-known system routines. 
--
    Todd M. Lewis / Todd_Lewis@unc.edu / utoddl@guitar.oit.unc.edu
"It isn't pollution that's harming the environment.  It's the impurities
 in our air and water that are doing it."  -- Vice President Dan Quayle
From: Lee_Robert_Willis@cup.portal.com
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  Comeau C++
Date: Tue, 13 Oct 92 19:07:39 PDT
Organization: The Portal System (TM)
Distribution: world
  <Bvs7F0.93B@well.sf.ca.us> <Bw25J7.DK3@well.sf.ca.us>

>Hmmm that triggers some more thoughts.  How do you debug C++ programs
>compiled
>with Comeau C++?  I think every one who does programming in C++ has seen
>the nasty names that are created by the front end as C-function names.

Hey Greg, why not include a name de-mangler utility with Comeau C++?
I know the mangling algorithm is in the docs, and were I ambitious
enough, I could write such a beast, but heck, yuz guys have already
got the code to do it already in the compiler, you just need to make
a tiny program which takes mangled name from standard input and writes
de-mangled name to stdout.

Other than that, I like my Comeau 3.0!

Lee      Lee_Robert_Willis@cup.portal.com

p.s.  When do the Sas 6.0 patches go out?  I need 'em.
Newsgroups: comp.sys.amiga.programmer
From: boberg@lysator.liu.se (Stefan Boberg)
Subject: Re: CATS address
Organization: Lysator Academic Computer Society, Linkoping University, Sweden
Date: Wed, 7 Oct 1992 13:44:49 GMT

fheitkamp@desire.wright.edu writes:

>In article <BvnMuM.K9C@unx.sas.com>, jamie@cdevil.unx.sas.com (James Cooper) writes:
>> 
>> In article <1992Oct5.020110.9906@newshub.ccs.yorku.ca>, wlanders@nexus.yorku.ca (W L Anderson) writes:
>>>I'm looking for the address of CATS to order the 2.04 autodocs & includes (or
>>>the 2.1 if they are available).  Can somebody send (or post), the address
>>>and/or cost?  Thanks.

>	How about the 3.0 includes?  Are they available? 

  To registered developers, yes. (All levels) But since KickStart 3.0 is
not available to the general public (it's currently only for developers 
and A4000 users) I seriously doubt that they are available to "anybody".

>> CATS doesn't sell direct, Department C does:
>> 
>>         Commodore Business Machines, Inc.
>>         Department C
>>         1200 Wilson Drive
>>         West Chester, PA  19380

>Fred Heitkamp,  ** Not an organization.  My opinions only **
--
Stefan Boberg - AP & EE student at Linkoping Institute of Technology, Sweden
 Author of LhA, ArjA and LhArcA. Co-author of Alien Breed, Project X ...
  EMail: boberg@lysator.liu.se, lha@augs.se           FIDO: 2:204/404.7
    UUCP:  {uunet|pyramid|rutgers}!cbmvax!cbmehq!cbmswe!team17!boberg
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.hardware
From: seifert@gn.ecn.purdue.edu (Michael S. Seifert)
Subject:  INPUT DEVICE problems...
Organization: Purdue University Engineering Computer Network
Date: Mon, 12 Oct 92 17:28:09 GMT

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.

struct IntuitionBase *IntuitionBase;
struct MsgPort *inputDevPort;
struct IOStdReq *inputRequestBlock;
struct Interrupt *handlerStuff;

struct InputEvent *__asm 
inputhandlercode(register __a0 struct InputEvent *keyevent)
{
if (keyevent->ie_Class == IECLASS_RAWKEY)
	if (keyevent->ie_Code == 0x14)  DisplayBeep(FALSE);
        /* PROGRAM CRASHES IF DISPLAYBEEP IS CHANGED TO SOMETHING
	   LIKE Tflag=TRUE;   */
return(keyevent);
}

/*  STANDARD INPUT HANDLER INSERTION CODE (I think)*/
main()
{
IntuitionBase = (struct IntuitionBase *)OpenLibrary("intuition.library",NULL);

if (handlerStuff=(struct Interrupt *)AllocMem(sizeof(struct Interrupt),MEMF_PUBLIC | MEMF_CLEAR))
{
if (inputDevPort = (struct MsgPort *)CreatePort(NULL,NULL))
{
if (inputRequestBlock = (struct IOStdReq *)CreateExtIO(inputDevPort,sizeof(struct IOStdReq)))
{
if (!OpenDevice("input.device",NULL,(struct IORequest *)inputRequestBlock,NULL))
{

handlerStuff->is_Code = (VOID (*)())inputhandlercode;
handlerStuff->is_Data = (APTR)NULL;
handlerStuff->is_Node.ln_Pri = 100;

inputRequestBlock->io_Data = (APTR)handlerStuff;
inputRequestBlock->io_Command= IND_ADDHANDLER;
DoIO((struct IORequest *)inputRequestBlock);		/*insert handler*/

Delay(1000);   /*  just delay for a while in this simple example */

inputRequestBlock->io_Command= IND_REMHANDLER;		/*remove handler*/
inputRequestBlock->io_Data = (APTR)handlerStuff;
DoIO((struct IORequest *)inputRequestBlock);
...



Newsgroups: comp.sys.amiga.programmer
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: SAS/C 6.0: schelp crashes w/KS1.2
Originator: jamie@cdevil.unx.sas.com
Date: Fri, 16 Oct 1992 16:14:14 GMT
Organization: SAS Institute Inc.


In article <1992Oct15.143152.7957@ugle.unit.no>, shansen@solan.unit.no (Stale L. Hansen) writes:
>When I compile and run schelp.c with KickStart 1.2 amigaguide
>"freeze" the machine when I try to drag the scrollbars with the
>mouse. If I start other programs (like CED) with 'schelp prg' they don't
>freeze when dragging scrollbars.
>With KS2.04 it works fine.
>
>I rewrote schelp.c to not use cback.o, and the all worked fine.
>
>Has anyone else experienced this? (Or am I the ONLY one who still
>use 1.2 ROMS ;-)
>Is this a bug in cback.o, AmigaGuide or Intuition (v33)?

What stack size do you normally run in your shell?

Try increasing the value stored in the __stack variable in schelp.c,
then recompile and try it again.  The stack may just be set too small
for your machine.

(And yes, 1.2 ROMs are getting more and more scarce... :-)

-- 
---------------
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.