HDTenEightyP/NetNews huggingface dataset:
From: bryanf@hpmcaa (Bryan Ford)
Subject: Re: Programming Tools (was: Amiga programmers UNITE)
Organization: HP Cardiology Business Unit - McMinnville, OR
X-Newsreader: Tin 1.1 PL4
Date: Fri, 14 Aug 1992 00:33:41 GMT

s37732v@vipunen.hut.fi (Markus Juhani Aalto) writes:
> In article <1992Aug11.153735.10768@samba.oit.unc.edu> utoddl@guitar.oit.unc.edu (Todd M. Lewis) writes:
> 
>    In article <1992Aug10.223432.27395@CS.ORST.EDU> divineg@prism.cs.orst.edu  
>    (Glade Diviney) writes:
>    >  What kinds of tools _DO_ they have?  Maybe an integrated C environment?
> 
>    The Interface Builder on the NeXT is an extremely powerful tool for
>    (you might guess) building user interfaces.  The debugger is also
>    pretty good.  That coupled with several hi-level IPC capabilities (cut
>    and paste just about anything anywhere, drop-in text editor, etc) make
>    it hard to make a program look bad even if it is.  
> 
> Does that interface builder allow you to make interfaces which
> automatically adapts to different fonts etc...
> [...]
> Agreed! GadToolsBox is a great start but it doesn't allow you to make 
> completely font independent interfaces (if I remember right).

I've already started into this area; if you've seen my program MultiPlayer 
you'll notice that all of its windows and gadgets (it has quite a few!) are
completely font independent.  The system I designed to handle this is called
Guido.  (The meaning of the first three letters are obvious; the other two are
just there to make it sound good. :-) )  It consists of a special compiler
that compiles GUI-definition pseudo-source-code into something that the
Guido runtime library uses to build user interfaces.  It's not an extremely
sexy way to design user interfaces, but I've found it very quick and simple
to use, and it would always be possible to build a graphical shell for it.

Of course, there are things I wish I had done differently with it, and 
some day I plan on rewriting it to be a little less obtuse in its internal
formats, more flexible, etc.  Until I get around to this, though, I'm not
quite sure what to do with Guido.  If somebody wants to work on a 
"next-generation" Guido of some kind, either based on Guido or simply
learning from it, I may consider releasing it under the GPL or LGPL.  (The
runtime part could be made into a shared library, and thus be usable by
commercial programs as well as freely distributable programs.)

So if anybody is interested, grab MultiPlayer and its source off amiga.physik
(Guido's source isn't with it, but the compiler, linked library, and basic
documentation are) and contact me (bryanf@hpmcaa.mcm.hp.com) if you want
more...

				Bryan Ford
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: IFF
Date: 21 Aug 92 23:31:33 GMT
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA

shf@well.sf.ca.us (Stuart H. Ferguson) writes:
>+-- mjp3783@ritvax.isc.rit.edu writes:
>| When C= introduced the Amiga, they (along with EA) produced a standard called
>| IFF. But the machine doesn't follow the standard. The standard is designed to
>| "package" any kind of data. According to the standard "File compatability is
>| easy to achieve if programmers let go of one notion -- dumping internal data
>| structures to disk."

>| What I am proposing is that ALL files that work with the OS should be
>| IFF format. Make anything the OS does use IFF's. This consistancy would 

	You may have noted that for 2.0, we made all the prefs files IFF.
We do like IFF, we also have various compatibility constraints.

-- 
"Rev on the redline, you're on your own; seems like a lifetime, but soon it's
 gone..."  Foreigner
-
Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
Newsgroups: comp.sys.amiga.programmer
From: val@news.ccutah.edu (Val Kartchner)
Subject: Re: SAS/C 6.0 Details (LONG!)
Organization: University of Utah Computer Center
X-Newsreader: Tin 1.1 PL3
Date: Tue, 18 Aug 92 20:36:29 GMT

walker@twix.unx.sas.com (Doug Walker) writes:
: 
: The following sections describe in more detail some of the changes and 
: enhancements to the SAS/C(r) Development System, Version 6.0.
: 
: Version 6.0 contains 1200 pages of all-new documentation, including
: a quick reference guide, library reference manual, and a two-volume
: user's guide.  Except for the quick reference guide, all documentation
: is in three-ring binders which lie flat while you work.
: 
: The SAS/C Development System has an extensive online help system
: implemented using AmigaGuide, a hypertext system from Commodore.
: The online help describes each utility, CodeProbe command, editor
: command, library function, diagnostic message, and compiler option.
: Help is available from within the editor, the debugger, the message
: browser, the options program and from the Shell command line.
: 
I'm looking forward to all of this.  Can a plain non-developer type get
AmigaGuide to develop (shareware/freeware) with?

: [...]
: You can designate autoinitialization functions that you want the startup
: code to call automatically before it calls your main routine.  You can
: also designate autotermination functions that you want the termination
: code to call after main returns.
: 
This is beginning to sound like C++.  When will SAS be releasing their C++
compiler. (I may wait or I may go with G++.)

: System library bases that are not defined in your code are automatically
: opened and initialized.  This means that you do not need to explicitly
: call OpenLibrary to initialize libraries such as intuition.library,
: graphics.library, and others.
: 
What exactly does this mean?  Does this mean that ALL Commodore provided
libraries will be openned and initialized, or ALL libraries currently
residing in the libs: directory, or something else?  This will take up a
lot of memory even if I don't need these libraries.

: [...]
I know that this version is 1.2, 1.3, and 2.0 compatible.  (I shouldn't
have deleted it from the posting.)  I hope that SAS continues to support
at least 1.3 for a while since I can't go beyond 1.3 with my A1000.  (I know,
but I may upgrade once the new AA chipset is out.)

--
|======================== The previous was my opinion =========///============|
| "AMIGA: The computer for the creative mind." (tm) Commodore /// Weber State |
| "Macintosh: The computer for the rest of us."(tm) Apple \\\///  University  |
|=================== val@csulx.weber.edu ==================\///=== Ogden, UT =|
From: dac@prolix.pub.uu.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: SAS/C and floats
Date: Thu, 13 Aug 92 12:40:45 GMT
Reply-To: munnari!labtam!eyrie!prolix!dac
FollowUp-To: comp.sys.amiga.programmer
 <1b7aa695.ARN229a@prolix.pub.uu.oz.au> <1992Aug10.215907.3351@desire.wright.edu>
Keywords: 
Organization: More like Dis~, really.

In article <1992Aug10.215907.3351@desire.wright.edu>, fheitkamp@desire.wright.edu writes:

> In article <1b7aa695.ARN229a@prolix.pub.uu.oz.au>, dac@prolix.pub.uu.oz.au (Andrew Clayton) writes:
> > In article <Bso3JB.6CB@unx.sas.com>, James Cooper writes:
> > 
> > Recently I recompiled a program, and it started producing really
> > bizarre figures for variables declared as 'double' - I suspect
> > some sort of memory trashing, but I'm too embarrassed about the
> > code fragment involved to post the problem.  :-/
> >
> 	You should use %lf for double.  This is a long float.

Tried this, and it didn't work. It looked promising though. :-)

Dac
--
Newsgroups: comp.sys.amiga.programmer
From: kxs5829@ultb.isc.rit.edu (K.X. Saunders )
Subject: GCC and __chip
Originator: kxs5829@ultb
Organization: Rochester Institute of Technology
Date: Fri, 21 Aug 1992 21:56:03 GMT

	Is there a way to specify that certaion .o files go into chip when
using Markus Wild's gcc-2.2.2 port?  Is there something similar to a __chip
keyword?

	- Kyle

-- 
+-"Remember, [MS]DOS is sort of a UNIX deviant already" - dmoscny@piglet.-----+
|    // Only /\          kxs5829@ultb.isc.rit.edu                 cincinatti. |
| \ //      /--\MIGA     kyle@nick.csh.rit.edu                    oh.us       |
| \X/ SQLdb - $40 rdbms  Rochester Institute of Technology                    |
From: mueller@schaefer.math.wisc.edu (Carl Douglas Mueller)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Ordering SAS/C Version 6
Date: 20 Aug 92 21:08:44 GMT
Reply-To: mueller@schaefer.UUCP (Carl Douglas Mueller)
Distribution: usa
Organization: Univ. of Wisconsin Dept. of Mathematics

In article <BtAsGE.J1E@news.cso.uiuc.edu> jmrg9881@uxa.cso.uiuc.edu (Jon Reid) writes:
>I just got my upgrade order form today.  There's one puzzling thing on it,
>and that's the sales tax.  Am I to understand that I need to tack on
>Illinois state tax (since I live in Illinois), even though SAS is in North
>Carolina?

As long as SAS has an office in a state, they must charge sales tax there
(I think that's the law ... but soon all the mail order places will charge
tax in all states).

>(The form says NOTE: Do not add tax on software shipped to the following
>states: AL, WI.)
             ^^^   :-)
Carl Mueller (mueller@math.WISC.edu)
From: tna@mentor.cc.purdue.edu (Trevor Andrews)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: GNU gcc/g++
Date: 16 Aug 92 05:01:12 GMT
Organization: Purdue University Computing Center

In article <1992Aug16.004649.23797@bernina.ethz.ch> wild@nessie.cs.id.ethz.ch (Markus Wild) writes:
>In article <56939@mentor.cc.purdue.edu> tna@mentor.cc.purdue.edu (Trevor Andrews) writes:
>>My problem is I want to do some work in C++ and do not want to have
>>to link with the excellent ixemul.library.  I know I know, not so easy.
>>Are there any other Standard Libraries availible for GNU gcc??
>
>Take a look on nic.funet.fi, there's at least one other library specially
>targetted for GNU C, it's written buy Ray Burr, and should be in the BuRP
>directory on nic, must be in the amiga subtree, in a directory called something
>like gnu/gcc/port/.. or the like, you'll find it ;-)

  I looked at Burr's stuff... Nice also... I guess I decided all I need
  is a gcc2hunk.  Well, basically I just need a C++ front for my
  Lattice compiler.

  Anyone know if a gcc2hunk exists for Markus Wild's GNU gcc!?
  Blinking with my other libs would be nice...  Hmm maybe I could
  write one...  Well, if I can't find one first. *smile*

>
>-Markus

  I still plan on using your alwsome port some how.

>
>
>-- 
>Markus M. Wild    -  wild@nessie.cs.id.ethz.ch  |  wild@amiga.physik.unizh.ch 
>Vital papers will demonstrate their vitality by spontaneously moving
>from where you left them to where you can't find them.

Thanks!
 
Take care,
  Trevor

~~        ___ 
         ////         tna@mentor.cc.purdue.edu (128.210.10.8, 128.210.33.1)
        //// 
   ___ ////   //                Imagine Software, Inc.
   \\\X///  \X/                 1218 South 5th Street
    \XXX/  Amiga                Lafayette, IN  47905-1716 U.S.A.
From: chrisg@cbmvax.commodore.com (Chris Green)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Safe double buffering
Date: 18 Aug 92 12:41:08 GMT
Reply-To: chrisg@cbmvax.commodore.com (Chris Green)
Organization: Commodore, West Chester, PA

In article <mcuddy.714096993@fensende> mcuddy@fensende.Rational.COM (Mike Cuddy) writes:
>What I'd like to do is to do the double-buffering like the example in the 1.3
>RKM and create two bitmaps, two views and two copper lists and swap them 
>with LoadView().  (not hard)  
>
>My question is:  Here's my proposed main page-flip loop... is this right 
>(legal?)

	Looks OK, except:
>
>	/* here's the part I have a question about... */
>	if (view.SHFCprList != cur_page_cpr_list[0] ) {
>	    /* open a window on workbench screen with a 'continue' 
>	    ** gadget in it... 
>	    */
	why are you checking for the SHFCprList in your view to change?
It won't change without you changing it (or calling mrgcop).
	You're not installing your own copper lists into the intuition view, are
you? That's certainly not legal or safe.
	What you should probably do instead is see if GfxBase->ActiView points
at your view.
-- 
*-------------------------------------------*---------------------------*
|Chris Green - Graphics Software Engineer   - chrisg@commodore.COM      f
|                  Commodore-Amiga          - uunet!cbmvax!chrisg       n
|My opinions are my own, and do not         - icantforgettheimpression  o
|necessarily represent those of my employer.- youmadeyouleftaholeinthe  r
|"A screaming comes across the sky..."      - backofmyhead              d
*-------------------------------------------*---------------------------*
From: rockwat@bbs1984.chi.il.us (Joe Ochwat)
Newsgroups: comp.sys.amiga.programmer
Subject: Perfect Sound 3.x Programming
Date: 18 Aug 92 18:49:19 GMT
Organization: Not an Organization

In order to do some programming with a Perfect Sound digitizer, do I have to
get ahold of some sort of source code, or programming package, from SunRize
Industries, or is there just some sort of "assumed" way of addressing parallel
port digitizers?  All I really need to do is get a program put together that
will find out when the sampler receives an audio signal, and preferably, at
what frequency or volume.  Is this a simple procedure?  I'm still very much a
novice programmer, familiar only with Basic and Arexx.  It would be optimal if
I could produce this program with AMOS, since the stuff I want to do with the
sampler information would be pretty suitable for the AMOS environment. 
Hopefully someone out there can help me!  Thanks much.

                                                                Hose
From: rwm@atronx.OCUnix.On.Ca (Russell McOrmond)
Date: 16 Aug 92 12:50:11 EST
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Speculations: Amiga and Mach?
	<56791@mentor.cc.purdue.edu>

bryanf@hpmcaa (Bryan Ford) writes:
>I never suggested that Commodore should abandon Amigas without MMUs.  That

  Developers need firewalls, users do not.  Developers use MMU based machines.
I've been suggesting that CBM attempt to make a 'developer specific' version
of the Amiga's O.S. that has all the MMU firewall protection in such a
way that more bug-free applications can be written.  Enforcer and Mungwall
are a good start, but they don't take care of many types of bugs that
could be detected.  I often get problems where I can't tell which
application I am running is actually causing the problem.

>				Bryan
--
  Opinions expressed in this message are my Own. I represent nobody else.
  Russell McOrmond  rwm@Atronx.OCUnix.On.Ca Net Support:(613) 230-2282(V.32Bis)
  FidoNet 1:163/109 Welmat Help 1:1/139  Current WELMAT 'keeper of sources'.
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Bug in 2.04 Autodocs -- LockDosList/UnLockDosList
Date: 21 Aug 92 22:14:53 GMT
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA

mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes:
>> 	The file docs/dos.doc in the 2.04 Autodocs (Native Developer's
>> Update) has an error. 

>> 		UnLockDosList(LDF_VOLUME | LDF_READ);	/* right */
>> instead of
>> 		UnLockDosList();			/* wrong */

>> 	I have also sent this information to bugs@cbmvax.commodore.com.

>Dan, please don't post this kind of message here.  You will leave people
>with the impression that the operating system isn't perfect :)
>
>THe OS 2.0 police are on their way to get you :)

	No, we would only be out to get him if he used that as justification
to forevermore force UnLockDosList to not take arguments... :-)  And he did
report it, so in fact I've already fixed it (thanks for the report, dan).

	Now the OS2 police may be out to get Dan, I wouldn't know.  ;-)

-- 
"Rev on the redline, you're on your own; seems like a lifetime, but soon it's
 gone..."  Foreigner
-
Randell Jesup, Jack-of-quite-a-few-trades, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Disclaimer: Nothing I say is anything other than my personal opinion.
From: dac@prolix.pub.uu.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Console file handlers from within a Shell started program
Date: Thu, 20 Aug 92 13:31:41 GMT
Reply-To: munnari!labtam!eyrie!prolix!dac
FollowUp-To: comp.sys.amiga.programmer
 <14605@borg.cs.unc.edu>
Keywords: 
Organization: More like Dis~, really.

In article <14605@borg.cs.unc.edu>, Stephen Tell writes:

> In article <1b854d0d.ARN237c@prolix.pub.uu.oz.au> munnari!labtam!eyrie!prolix!dac writes:
> >In article <14545@borg.cs.unc.edu>, I wrote:
> 
> >If I redirect stdout via '>', then I get the stderr output on the
> >console, and not in the redirected output.
> 
> >Where is the problem?
> 
> Now, show me how to put stderr in a file and let stdout go to the console...
> and how to put stderr in one file and stdout in another.  Can't be done, to
> my knowledge.

Er, right.

Well why not just open a file whose name is specified on the
command line call, if it's that important to do such stuff. Or
use 'Tee' in CSH, or something like that. I guess some knowledge
of the application's requirments would help.

:-)

Dac
--
"Polka your eyes out" by Weird Al Yankovic, is weird.
From: rwm@atronx.OCUnix.On.Ca (Russell McOrmond)
Date: 21 Aug 92 10:03:55 EST
Newsgroups: comp.sys.amiga.programmer
Subject: Re: SAS/C 6.0 Details (LONG!)

walker@twix.unx.sas.com (Doug Walker) writes:

>There was some discussion about 1.3 support in our beta tester 
>conference on BIX at one time, with feelings about equally divided

   All I hope is that a '2.0 only' install exists.   When
installing 5.10 I had to install everything, and then delete all
the 1.3 crap.  All the update scripts (5.10a, 5.10b) had to be done
manually because they would barf with the redundant disk space re-claimed.
While supporting 1.3 is one thing, having switches to turn that support off 
is great.   I myself don't use many of the built-in SAS routines because
they add too much code when 2.0 equivalants exist (simple RawDoFmt() instead
of sprintf() and PutStr instead of print/etc).  Having shipped startup code 
that allows for the amiga.lib stubs to be used for stdio/etc instead of SAS
additions would be great.

  I got my upgrade notice last night.  I need to be convinced that this
upgrade is actually worth another $109+shipping for myself. The
'tagcall' pragma is about the only thing that hit me as interesting, and
I can't think that it's worth $109 ;-)


  Out of curiosity, what revision of the 2.0 includes are being shipped
with it?  Will I have to re-install CBM includes right away (As I did not
soon after getting 5.10)

>  *****
>=*|_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.
--
  Opinions expressed in this message are my Own. I represent nobody else.
  Russell McOrmond  rwm@Atronx.OCUnix.On.Ca Net Support:(613) 230-2282(V.32Bis)
  FidoNet 1:163/109 Welmat Help 1:1/139  Current WELMAT 'keeper of sources'.
From: rse@angle.sub.org (Ralf S. Engelschall)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Pascal for the Amiga
Date: Thu, 20 Aug 1992 16:42:29 GMT
Reply-To: rse@angle.sub.org
X-Newsreader: Arn V1.00 beta rel3

In article <1992Aug17.143101.4982@mits.mdata.fi>, Risto Kaivola writes:

>   Is there a Pascal compiler system with a source-level debugger available
> for the Amiga (perhaps HiSoft ?), and if so, at what price?
>   If not, is there a need for such a thing?

  I used the P2C (Pascal To C) package in conjunction with my SAS/C
Compiler and it works great.  To debug, I take the CodePRope (CPR) from
SAS/C, because P2C converts the Pascal source directly into a C source.
Another reason to use this tool was the fact that P2C understands a lot
of Pascal versions (I compiled VAX Pascal sources and it worked great!).

  P2C is a port of the UNIX P2C tool.  I have found it on a FTP archive
in Germany, but it can be found on many others sites on the world.
                              ___  _______
                              /__)(_  /_    Ralf S. Engelschall
                             / \____)(___   rse@angle.sub.org
                            /
From: kentd@FtCollins.NCR.com (Kent Dalton)
Newsgroups: comp.sys.amiga.programmer
Subject: ixemlib manual?
Date: 11 Aug 92 22:16:05 GMT
Reply-To: Kent.Dalton@FtCollinsCO.NCR.com
Distribution: world
Organization: NCR Microelectronics, Ft. Collins, CO


Is there any manual available (aside from the header files :^) for
Markus Wild's ixemul UNIX emulation library? I'm porting some pretty
heavy UNIX code to my Amiga and I could really use some kind of guide
for what's implemented and how it deviates from "normal" UNIX sdystem
library behavior.  Even a list of functions would help...

I couldn't find any documentation other than a readme in the
distribution I got.

Also, does anybody know where can I ftp the gcc 2.0 base release so I
can cross-compile on my Sparc? I checked prep.ai.mit.edu but they only
had 1.4 and 2.2 kits there...
 
--
/**************************************************************************/
/* Kent Dalton                   * EMail: Kent.Dalton@FtCollinsCO.NCR.COM */
/* NCR Microelectronics          * Phone: (303) 223-5100 X-319            */  
/* 2001 Danfield Ct. MS470A      *   FAX: (303) 226-9556                  */
/* Fort Collins, Colorado 80525  *                                        */
/**************************************************************************/
All of a sudden, I want to THROW OVER my promising ACTING CAREER,
 grow a LONG BLACK BEARD and wear a BASEBALL HAT!!
 ...  Although I don't know WHY!!
Newsgroups: comp.sys.amiga.programmer
From: vinsci@nic.funet.fi (Leonard Norrgard)
Subject: Re: Speculations: Amiga and Mach?
Organization: Soft Service, Inc.
Date: 17 Aug 92 22:41:18

In article <64173@cup.portal.com> Tony-Preston@cup.portal.com (ANTHONY FRANCIS PRESTON) writes:
> Having worked with "porting" applications into the Mach environment
> I would say that moving Amigados to Mach(similar to what I did with
> a different Real time system in Ada) would be a mistake.  Mach documentation
> makes the RKM and other Amiga documentation look like a set of 
> detailed instructions!  My vote is to say aways from Mach at this time!

What do you need documentation for, when you have the source?
Besides, the idea is to put AmigaOS *on top of* Mach, an operation
that is likely to be completely invisible to Amiga applications and
programmers.  There will be ways to call Mach from AmigaOS, but this
doesn't affect software in a negative way.  Thus the only people to
need Mach documentation are those who need to interact directly with
Mach.

-- Leonard