HDTenEightyP/NetNews huggingface dataset:
From: hemmer@hemmer.adsp.sub.org (Franz Hemmer)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Version Strings...
Date: 8 Jan 93 17:50:24 GMT
Reply-To: hemmer@hemmer.adsp.sub.org (Franz Hemmer)
Organization: Interactivsion
X-NewsSoftware: GRn-beta 1.16g (11.15.92) by Michael B. Smith & Mike Schwartz

In article <Leon.0byx@abcd.Houghton.MI.US> Leon@abcd.Houghton.MI.US (Leon) writes:
> Can anyone give me a code fragment to insert a version string in my program
> so that the AmigaDOS version program will detect it?

Example:

UBYTE *VersTag = "\0$VER: Watcher 39.21 (11.12.92)";

Get a hold of BumpRev which can create these tags automatically an update
the revision counter.

--
Best regards                    Reply to: hemmer@hemmer.adsp.sub.org
Franz Hemmer                    #include <stddisclaimer.h>
Software Developer       _      >> Carpe Diem! - Seize the day! <<
                         \\ _
                 Interacti\X/ision - The name of precision
From: cs_e445@ceres (Vlod Kalicun)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: OS 'Move/Draw' speed
Date: 11 Jan 1993 14:23:11 GMT
Organization: Kingston University
NNTP-Posting-Host: ceres.kingston.ac.uk
X-Newsreader: Tin 1.1 PL4

bloc1469@ee.ee.uwm.edu (Gregory R Block) writes:
: You've got a 68000?  It's officially slow.  :)  Listen, unless you're
: writing your pixels to the screen randomly, there is a more
: "efficient" way of doing it -- Use WritePixelArray8 or
: WritePixelLine8, depending on your application.  If you're doing
: horizontal lines, you may want to use WritePixelLine8.
: 
: They're a _LOT_ faster.  :)
: 
: Greg

Hmmm.. Im a student! Im officially poor!! ;-) 
Okay.. will try out those functions.. thanks.

Regards..

Vlod
-Amiga Advocate.
----------------------------------------------
Amiga - Anything else isn't worth considering
----------------------------------------------
Newsgroups: comp.sys.amiga.programmer
From: iikoch@techfak.uni-bielefeld.de (Ingolf Koch)
Subject: Re: Amiga an TEX
Date: Thu, 7 Jan 1993 15:33:21 GMT
Organization: Universitaet Bielefeld, Technische Fakultaet.

In article <1993Jan7.143649.28420@samba.oit.unc.edu>, Todd_Lewis@unc.edu (Todd M. Lewis) writes:
|> Tomas Rokicki's TeX package includes a previewer.  A demo version
|> is on Fred Fish Disk #83 (that's right, two digits--way back when).
|> (If source is what you want then this won't do you any good.)

Hello,
IMHO the previewer which is included in the PasTeX package (by Georg Hessmann)
is ingenious. This package is PD (in this case, it doesn't mean low quality)
and can be found on various servers.

Bye
-- 

Ingolf Koch				Wellenkampstrasse 38
					W-4937 Lage, Lippe
					Germany
iikoch@techfak.uni-bielefeld.de		Phone: 05232 / 2700
Newsgroups: comp.sys.amiga.programmer
From: breese@monet.imada.ou.dk (Bjoern Reese)
Subject: Re: OS 'Move/Draw' speed
Organization: Dept. of Math. & Computer Science, Odense University, Denmark
Date: Mon, 11 Jan 1993 15:33:02 GMT

In article <1993Jan11.170422.45@iwsd01.itwol.bhp.com.au>  
wenicp@iwsd01.itwol.bhp.com.au (Peter Nicholson) writes:
> In article <1993Jan7.115153.1364@imada.ou.dk>, breese@monet.imada.ou.dk  
(Bjoern Reese) writes:
> > "Real programmers" make their own blitter line routines (some of which
> > can be found on some ftp sites - I forgot where)
> 
> Could anyone point me in the direction of such a routine? I have an old
> hardware reference manual, but it doesn't explain how to do this.
> (I also have the Abacus System Programmers Guide, but their routine
> doesn't seem to work).

Ftp an aminet site (like amiga.physik.unizh.ch) and look for:

/pub/aminet/text/docs/tipdrwln.lha

(I'm not quite sure about the path though.)

--

Bjoern Reese                   |     Email: breese@imada.ou.dk
Odense University, Denmark     |     Voice: +45 65 932 182 (private)
Newsgroups: comp.sys.amiga.programmer
From: Todd_Lewis@unc.edu (Todd M. Lewis)
Subject: Re: Version Strings...
Organization: UNC Office of Information Technology
Date: Fri, 8 Jan 1993 14:53:23 GMT

In article <1993Jan8.111612.25180@sunbim.be> accs1@bagheera.mumath writes:
>
>>UBYTE Version[] = "\0$VER: ProgName 1.0 (7.1.92)";
>
>I wonder why that stays in the executable. I would expect a good compiler  
>would through that line away unless it is really referenced.

It _IS_ really referenced--by the Version program.  I'm not sure I would
call a compiler "good" if it started getting in the way building programs.
Perhaps a "really good" compiler would have an option to turn off some
optimizations in selected places.
--
 _/_/_/  _/     Todd_Lewis@unc.edu          You can lead a horse to 
  _/    _/     utoddl@guitar.oit.unc.edu   Mohammad, but you can't make
 _/    _/_/_/                             a mountain drink a mole hill.
From: f92anha@fy.chalmers.se (Anders Hammarqvist)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Version Strings...
Date: 10 Jan 93 17:33:52 GMT
Organization: Chalmers University of Technology

In article <1in6s9INNnhl@flop.ENGR.ORST.EDU> brindley@maxwell.ECE.ORST.EDU (Mike Brindley) writes:
>In article <C0HyvD.D5z@DMI.USherb.CA> vailm00@DMI.USherb.CA (MARC VAILLANCOURT) writes:
>>-> Can anyone give me a code fragment to insert a version string in 
>>-> my program so that the AmigaDOS version program will detect it?
>> 
>>   No problem, here is an example:
>> 
>>static char *VerString = "$VER: Hyper-Snake 0.95 (29.10.92)";
>
>This may be obvious, but here goes anyway :)
>
>Please make sure that the version string is near the beginning of the 
>executable, so that the version command can quickly find it.  This can
>normally be achieved by placing the code above (or similar code) at
>the top of one of the programs modules, and then making that module the
>first one in the link command.

That won't work if you use the (equivalent of SAS's blink) SMALLDATA
option, since that merges all the data segments. You're better off
putting it in a small assembler file and saying it is code, ie:

	csect code
	dc.b '$VER: Hyper-Snake 0.95 (29.10.92)',0
	end

and linking that as the second module.

Anders, f92anha@fy.chalmers.se
From: gujn@uniwa.uwa.edu.au (Jeremy Nelson)
Newsgroups: comp.sys.amiga.programmer
Subject: How to allocate memory nicely?
Date: 5 Jan 1993 10:39:46 +0800
Organization: The University of Western Australia
NNTP-Posting-Host: uniwa.uwa.edu.au

This is probably a simple question for the programmers, so reply by news
or mail as you see fit...

How should I allocate memory for short strings of, say, 15 characters or
so without unnecessarily fragmenting the memory?   Should I request 1k
chunks and doll it out as necessary?  And how small is too small?

Help from the experienced would be appreciated.  Thanks. (I'm talking 
C of course. :)
-- 
Jem.  Jeremy Nelson.  gujn@uniwa.uwa.edu.au       :\  =>  :)
From: mbs@adastra.cvl.va.us (Michael B. Smith)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GCC signal handling bug
Distribution: world
X-NewsSoftware: GRn-beta 1.16g (04.01.93) by Michael B. Smith & Mike Schwartz
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Date: 8 Jan 93 20:54:27 EST
Organization: Well, I haven't decided on a name yet...

In article <SIE.93Jan8094837@introitus.fulcrum.co.uk> sie@fulcrum.co.uk (Simon Raybould) writes:
> On the amiga, I have to press return after the ^C for it to see it
> which I don't have to do on the SUN. Also the ^C is only seen if it is
> on the first line typed, i.e. before the first newline.
>
> The ^C is only seen it I comment out the puts() line, with this line,
> the signals are ignored.
>
> Any advice much appreciated, this is stopping me finishing a rather
> important project.

I don't have any good news for you. That is the way Markus built stdio.
There are a variety of reasons, and my memory on them is foggy, but they
made sense at the time.

Someone runs into this every couple of months.

I suggest that you don't use stdio and use read()/write() with FNONBIO.
That is, roll your own.
--
  //   Michael B. Smith
\X/    mbs@adastra.cvl.va.us  -or-  uunet.uu.net!virginia.edu!adastra!mbs
Newsgroups: comp.sys.amiga.programmer
From: ruffalom@cs.uwp.edu (Mike Ruffalo)
Subject: SA_Pens
Organization: University of Wisconsin - Parkside
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 11 Jan 1993 18:18:05 GMT


	Help! When I set the SA_Pens tag up like described in the RKM 'manuals'
(so as to recieve the 3d v37OS GUI) I loose the fg/bg pen in the system
requesters! In the req.library requesters as well. Though when I comment
out the SA_pens,[displayinfohere], tag the readability comes back.

	Anyone have an light to shed? There is only one prime example of
the SA_Pens tag usage in the RKM and the other are redundent.

	Thanks in advance
-- 
///////////////////////////////////////////////////////////////////////////
			PANIC NOW AVOID THE RUSH!
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
From: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Newbie font/screen question
Date: 8 Jan 93 08:23:58 GMT
Reply-To: peterk@cbmger.de.so.commodore.com (Dr Peter Kittel Germany)
Organization: Commodore Germany

In article <Qvlbs*2a2@swinjm.adsp.sub.org> forgeas@swinjm.adsp.sub.org (Jean-Michel Forgeas) writes:
 >In article <paulk.2vmr@terapin.com>, Paul Kienitz writes:
 >
 >> At some time in the past I found that calling OpenDiskFont() will
 >> always load from disk even if the font is already in memory.  So I
 >> call OpenDiskFont() only if OpenFont() fails.
 >
 >It's true, 

Hhmmmmmmm. I simply use OpenDiskFont() since 1.3, and in *my* programs
it does *not* load the font everytime from disk (as long as there is
enough RAM to cache this font). What am I doing wrong???

-- 
Best regards, Dr. Peter Kittel  // E-Mail to \\  Only my personal opinions...
Commodore Frankfurt, Germany  \X/ {uunet|pyramid|rutgers}!cbmvax!cbmger!peterk
Wer's nicht kann, soll's bleiben klopfen oder Steine lassen!
From: lionet@lionfl.adsp.sub.org (Francois Lionet)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: LoadView(0) and sprites: bug in kickstart?
Date: 7 Jan 93 12:43:07 GMT
Reply-To: lionet@lionfl.adsp.sub.org (Francois Lionet)
Organization: Not an organization
X-Newsreader: Arn V1.00 alpha rel2

In article <1993Jan4.013803.5167@news.uit.no>, Boerge Noest writes:

> Now, I LoadView(0) and thought all was ok until a friend of mine tested it
> on his 4000 and said 'seriously slim sprite of yours'. He use a superhires
> pointer and my sprite was displayed in superhires too.

I had exactly the same problem with AMOS. The solution is simple (that's 
why it took me a long time to find!).

Just before taking over the hardware (well, branching your copper list), and 
BEFORE calling LoadView(0), open a simple, lowres screen, using OpenScreen from
intuition. This will force the lowres screen in front of intuition screen,
change the resolution of the monitor, and force the sprites back to normal.
Then performs two WaitTOF, time for Intuition to correctly update the
sprites.
Limit the bitmaps to 1 bitplane, and as small as possible to avoid loss of
memory. But after all, any AA machine have got 2 megs minimum.

Now you can do your LoadView(0) + WaitTOF + WaitTOF as recommended
by Commodore. It works fine even in the trickyest resolutions like
DBLPal or DBLNtsc...

Upon quitting you software, just reload the default view and then
close your small screen.

> Thanks.
My pleasure.
--
                    "The words of AMOS: proclaim free-will and publish!" 
                    (Old Testament, AMOS 4.5)
Francois Lionet           
cbmvax!cbmehq!cbmfra!lionfl!lionet
lionet@lionfl.adsp.sub.org
Newsgroups: comp.sys.amiga.programmer
From: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: Version Strings...
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Sat, 9 Jan 1993 01:18:01 GMT

In article <24661@hacgate.SCG.HAC.COM> johnl@SDFSERV.hac.com (John Lee) writes:
>In article <Per_Salmi.0lxs@augs.se> Per_Salmi@augs.se (Per Salmi) writes:
>>accs1@bagheera.mumath wrote:
>>: In article 93Jan7184001@lk-hp-16.hut.fi, s37732v@snakemail.hut.fi (Markus Juhani Aalto) writes:
>>: >In article <Leon.0byx@abcd.Houghton.MI.US> Leon@abcd.Houghton.MI.US (Leon) writes:
>>: >UBYTE Version[] = "\0$VER: ProgName 1.0 (7.1.92)";
>>:
>>: I wonder why that stays in the executable. I would expect a good compiler
>>: would 
>>: through that line away unless it is really referenced.
>>
>>You really got a point there! Why does it? 
>
>....  By then, it's too late since the
>linker can't throw out things in a module.

What can't it throw it away?  (I obviously feel it can).

>Now, if it had been declared:
>
>	static UBYTE Version[] = "\0$VER: ProgName 1.0 (7.1.92)";
>
>then the compiler might have noticed the lack of references and
>optimized it away.

Which leads to the earlier question of: but should it.
I certainly don't want nonsense cluttering up my executables,
OTOH, there are things like Version (I've seen similar on other systems
and have even written said type of situations myself), and other things.

- 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: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: How should I learn C?
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 7 Jan 1993 07:54:06 GMT

In article <1993Jan7.002116.21316@netcom.com> fletcher@netcom.com (F. Sullivan Segal) writes:
>>
>In any case, for advanced programming features, C to C++ is an easier
>step than anything else I can think of.

There are gotcha's with everything.  But yes, a smooth transition is
very possible and many have successfully done it properly.

- 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: Hardware bashing demo takes an OS friendly turn.
Organization: UNC Office of Information Technology
Date: Thu, 7 Jan 1993 15:26:09 GMT

In article <1993Jan7.113238.1139@imada.ou.dk> breese@monet.imada.ou.dk (Bjoern  
Reese) writes:
>The recent discussion on hardware bashing made me wonder if I
>could adjust one of my demos to be more OS friendly.[...]

>I had to give up using WaitBlit() in preference of testing the
>BBUSY bit in the dmaconr hardware register by myself. Using
>WaitBlit() increased the execution time about 1/5 of a frame
>(which I could afford), but as I depended on the preservation
>of all data registers and most address registers I had to dump
>the scratch registers on the stack, which increased execution
>time about 1/2 frame (and that I couldn't afford).

You toasted yourself.  Here, have a quote from the AutoDocs for
WaitBlit():
   RESULT
       Your program waits until the blitter is finished.
	This routine does not use any the CPU registers.
	do/d1/a0/a1 are preserved by this routine.
	It may change the condition codes though.
Otherwise, it looks like you've done a nice job.  Thanks for
posting the code.

>Bjoern Reese                   |     Email: breese@imada.ou.dk
--
 _/_/_/  _/     Todd_Lewis@unc.edu          You can lead a horse to 
  _/    _/     utoddl@guitar.oit.unc.edu   Mohammad, but you can't make
 _/    _/_/_/                             a mountain drink a mole hill.
From: bloc1469@ee.ee.uwm.edu (Gregory R Block)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: RKM description of WaitPort()
Date: 5 Jan 1993 05:53:50 GMT
Organization: Electrical Engineering Dept. University of Wisconsin - Milwaukee
NNTP-Posting-Host: 129.89.2.33

In article <1993Jan1.221013.26070@urbana.mcd.mot.com> qbarnes@urbana.mcd.mot.com (Quentin Barnes) writes:
>It seems to me to OS is waking up the task before it has attached the
>message to the specified port and it would be up the the application
>to spin on the GetMsg() call until the message generating the signal
>showed up.  This seems terribly wrong and the example code does not
>do this.  What am I missing?  What does the documentation actually
>saying?

No, it's just possible to send a signal to a port without sending a
message.

Greg


--
(: (: (: (: Have you overdosed on smileys today?  Why NOT!?! :) :) :) :)
(: "Our father, who art in Iowa, Hollow be thy head, Thy ideas run    :)
(:  Thy will be done, At Commodore as it is at Apple"  -Dan Barrett   :)
(: (: (: (: (: (: (: (: (: (: (: (: () :) :) :) Wubba, the Dark Angel :)
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: Upgrade MANX C for ADOS 3.0 stuff? How?
Originator: walker@twix.unx.sas.com
Date: Mon, 11 Jan 1993 13:56:13 GMT
Organization: SAS Institute Inc.


In article <73230@cup.portal.com>, plav@cup.portal.com (Rick M Plavnicky) writes:
|> environment, but I find it quite confining.) It'll kinda bum me out to
|> end up switching to SAS for current support, and having to a) learn a
|> new way of doing things, and b) figure out how to get all the GUI
|> stuff out of the way without losing too much functionality. 

You will have to do (A), but not (B).  The GUI stuff is NOT required
at all.  The command-line compiler and make utility combination works
every bit as well as the GUI.

That said, the SCOPTIONS file (which contains compiler command-line
options in ASCII-readable format) is a useful addition to the 
traditional CLI method, and the GUI program for reading and setting
these options *is* convenient, even for CLI users.  If you know the
option you want to set, for example OPTIMIZE to turn on the 
optimizers, just type

   SCOPTS OPTIMIZE    or     SCOPTS OPT

and it gets added to your SCOPTIONS file.  You can turn previously-
specified options off as well as adding new options:

   SCOPTS NOOPTIMIZE   or    SCOPTS NOOPT

will remove the previously-specified OPTIMIZE option.  If you don't
know the options, just invoke SCOPTS with no options, and the GUI
pops up, with gadgets for each compiler option.  Place the mouse
cursor over a gadget and hit HELP, and you get information on
the corresponding option.

There is a section in our manual that tells you how to convert
Aztec C options to SAS/C V6.0 options.  That might help a bit...
also, I have put a Un*x-like front-end to the V6 stuff out as
freely redistributable software, with source.  It's called
ucc.lzh.  Using this would mean you wouldn't have to change your
basic -c, -o, -g and -i options, along with a couple of others.

|> Aside to Doug Walker: How long will the Manx-->SAS upgrade deal you
|> recently mentioned last?  Another week or two?  Indefinitely?
|> Somewhere in between? 

That's really up to the marketing folks, but there are no plans that I
know of to withdraw the offer.

|> /* Rick Plavnicky  plav@cup.portal.com */

-- 
  *****
=*|_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
From: bandy@netnews.jhuapl.edu (Mike Bandy)
Subject: Re: Arexx question
Organization: JHU/Applied Physics Laboratory
Date: Fri, 8 Jan 1993 17:12:41 GMT

burton@latcs1.lat.oz.au (James Burton version 1340) writes:

>>I have a simple question about Arexx... I want for my Arexx program to
>>sit and wait for say 3 minutes or so, and then continue on with the program.
>>How do I get ARexx to do that without~r using up much processor time?
>>The loop that I tried didn't work too hot.  8-)  There must be a command
>>that does this??? Anybody?  Thanks.
>>

>Yes, I would be interested in this.
>If you try to do the following
>'c:wait' 50
>from an AREXX program, it does not wait.
>I suppose it backgrounds the shell task.
>Can somebody please confirm this?
>I find it extremely annoying.

In my ADPro scripts I use the following to sleep 3 seconds:
     PAUSE 50*3
Offhand (I'm at work without an Amiga manual handy), I'm not sure if 
PAUSE is an ADPro thing, or an Arexx thing.  So, to sleep your 3 
minutes, you'd do:
     PAUSE 50*180

Try it!

-- 

	Mike Bandy
	bandy@aplcomm.jhuapl.edu
	Johns Hopkins University / Applied Physics Lab
From: dvljrt@cs.umu.se (Joakim Rosqvist)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: OS 'Move/Draw' speed
Date: 9 Jan 93 18:16:14 GMT
Organization: Dep. of Info.Proc, Umea Univ., Sweden

>Yep, writing single pixels is slow. Mainly because it needs to convert
>an x,y coordinate to memory addresses and probably do some clipping.
>The function call itself also adds some overhead.

WritePixel is slow mainly because it uses the blitter.
Why waste 6-8 chipram accesses to tell the blitter how to plot a pixel
when the CPU can do it by itself with 2 accesses?

							      '''
/Joakim Rosqvist, $DR.HEX$)  Email: dvljrt@cs.umu.se	     (o.o)
---------------------------------------------------------oOO--(_)--OOo-----
Amiga coders do it 50 times per second.
From: johnv@acix.DIALix.oz.au (John Verhoeven)
Subject: C++ novice quesions
Newsgroups: comp.sys.amiga.programmer
X-Newsreader: TIN [version 1.1 PL8]
Date: 10 Jan 93 16:36:11 WST
Organization: ACix - Private UUCP Node, Cloverdale, Western Australia.

I'm trying to learn C++ using the book 'C++ Primer, Stanley Lippman, 2nd
Edition' and have typed in one of the examples from the book.

When I try and compile it I get several errors.

Does anybody know where I can get explanations for the error messages
put out by GCC?

Here is the types of errors I am getting:

intarray.cc:5:  `IntArray::IntArray (int (= ArraySize ))' is already
    defined in aggregate scope

intarray.cc:45: parse error at end of input

What level of C++ does gcc conform to?
From: sheun@cs.city.ac.uk (Sheun Olatunbosun)
Subject: Replies to DD vs HD posting
Keywords: Thanks
Organization: City University
Date:  6 Jan 93 12:57:46 GMT

Thanks to everybody who replied to my posting, via the net or email. It's nice
to receive an abundance of replies to a problem which has probably been 
mentioned on this newsgroup before.

Sheun
Newsgroups: comp.sys.amiga.programmer