HDTenEightyP/NetNews huggingface dataset:
From: jamie@cdevil.unx.sas.com (James Cooper)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Bug in SAS/C 6.0
Keywords: SAS/C
Date: 14 Oct 92 13:15:38 GMT
Organization: SAS Institute Inc.
Originator: jamie@cdevil.unx.sas.com


In article <1992Oct13.220109.26332@uni-paderborn.de>, tron@uni-paderborn.de (Matthias Scheler) writes:
>
>       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.

How about a bug report to SAS Tech Support, so the problem can be fixed?

EMITS is described in the User's Guide, Volume 1, starting on page 31.

How about some sample code, so we can see if it is the compiler, or your
code causing the problem?

-- 
---------------
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: csg019@cck.coventry.ac.uk (-~=Zaphod=~-)
Newsgroups: comp.sys.amiga.programmer
Subject: Come in number 2...
Date: 15 Oct 92 12:55:57 GMT
Organization: Coventry University


ATTENTION 

    andre@andrez.equinox.gen.nz
    phill%UUCP.nebul%.UUCP.equinox@UUCP.fmlg
    
I tried to mail you the 68k assembly code you wanted, but it bounces!

Mail me again!

-- 
******************************************************************************
*        ///  O O   A member of S.H.I.T. (Super High Intelegence Team)  ///  *
*       ///    u    Fight, defeat and kill organized laming.           ///   *
****\\\X//****\-/********csg019@uk.ac.cov.cck ok ?**************** \\\X//*****
From: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: AREXX parsing madness  -- will it ever be fixed?
Date: 14 Oct 92 19:39:43 GMT
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA

taylorm@wl.aecl.ca writes:
>dylan@cs.washington.edu (Dylan McNamee) writes:
>> 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...
>>
>
>If it is any consolation to you, the OS2 2.0 version of REXX does exactly the
>same thing.  I just installed OS2 2.0 at work and have been writing a few
>REXX scripts.
>
>The nice thing about OS2 REXX is that it will interpret anything that isn't
>a REXX command to be an OS2 command.  In AREXX you have to create a
>temporary script file and execute it or put the command into the queue which
>won't get executed until after the rest of the AREXX program is done.

This is not true.  If the script was started from the shell the default
host is the shell and thus any unknown command will go to the shell.
If the script is started from, say, TurboText, any unknown command goes
to TurboText.  This is known as the COMMAND HOST of the Rexx script.

ARexx fully follows the language specification on REXX COMMAND HOSTS.

>This is my biggest complaint with AREXX.  At least Commodore had the good
>sense to include AREXX as part of the OS.

Well, I guess you will need to find a different one  ;^)

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///                                                                |
| \XX/                      HELP!  I am starting to like it here...    |
\----------------------------------------------------------------------/
From: app@shamash.cdc.com ( GSD Advanced Packing/Processes)
Newsgroups: comp.sys.amiga.programmer
Subject: Hidden Line Problem
Date: 14 Oct 92 21:13:48 GMT
Organization: Control Data, Arden Hills, MN

Looking for source code for "General Solution to the Hidden-Line Problem" by 
David Hedgley Jr. Description of algorithm was in a NASA reference publication
#1085 dated March 1982.
                               Thanks
From: cheungc@p4.cs.man.ac.uk (Carson Cheung)
Newsgroups: comp.sys.amiga.programmer
Subject: Standard ML On The Amiga
Date: 15 Oct 92 15:03:25 GMT

Does anyone know if there is a version of
Standard ML available for the Amiga and where I can
get it from.

Replies by e-mail please

Thanks in advance

Carson Cheung
From: wille@june.cs.washington.edu (Robert Wille)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: IDCMP
Date: 9 Oct 92 18:45:25 GMT
Article-I.D.: beaver.1992Oct9.184525.19386
Organization: University of Washington Computer Science

In article <Bvu6pz.JMs@fiu.edu>, xnybpf01@serss0 (Brian P Feeny) writes:
|> 
|> 	I have a question that I hope someone can help me with.  I need to 
|> write a routine that basically waits for a disk to be inserted.  This routine
|> will run in the background at all times.  I do NOT wish for this routine to
|> open a window.  So how do I get IDCMP messages when I dont have a MsgPort
|> connected to a window?  I would like this program to be ran, and then you can
|> just get on with your work, when a disk is inserted, the progm will hear
|> about this, yet be quiet that it knows.  Some direction in C please.
|> 
|> 						Brian
|> -- 
|> Brian Feeny - Systems Programmer - UNIX System Security Specialist
|>    __
|> __///          Internet: signal@phantom.com       "Grep me no patterns and
|> \XX/ AMIGA!              xnybpf01@serss0.fiu.edu   I'll tell you no lines"

I have a really nice example for you, but my mail to you bounced.

-- 
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.
From: rouaix@inria.fr (Francois Rouaix)
Newsgroups: comp.sys.amiga.programmer
Subject: Bunch of DICE questions
Date: 12 Oct 92 17:10:34 GMT
Distribution: comp
Organization: INRIA Rocquencourt, France

To Dice users out there, I submit a  few questions. This is in case I
missed something in the doc. If you know an answer for sure, please 
enlighten me.

1- register allocation:  the compiler ignores all "register"
qualifiers. If the optimiser is not that smart, a variable may end up
on the stack, whereas you really wanted it in a register. Is there a
way to *force* a variable to be in a register ?

2- Unix path compatibility and incompatibility in dcpp: there is one
thing I don't understand.
#include "../../config/m.h"
works, even if I actually meant
#include "//config/m.h".
On the other hand, I wanted to do
dcc -I /runtime foo.c
and the compiler keeps asking me to insert volume runtime. Is that a bug ?

3- Did anybody get the following error message: "macro crosses line boundaries"
My manual says I should never see it.

4- -gs option (growing stacks): the manual says this option is still
in beta-test, and advises against using it in a released program. 
Did anybody have any problems with it ? 

Thanks for any help on these questions.
(If it matters, I'm running 2.06.40R in 2.04)
--
Francois Rouaix                         Projet Chloe - INRIA Rocquencourt
rouaix@margaux.inria.fr
Newsgroups: comp.sys.amiga.programmer
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: Defect: SAS/C "se" (screen editor)
Originator: jamie@cdevil.unx.sas.com
Date: Mon, 12 Oct 1992 14:56:02 GMT
Organization: SAS Institute Inc.


In article <18734.2ad894a8@ecs.umass.edu>, bell@ecs.umass.edu writes:
>In article <fgd3.02br@nifty.UUCP>, fgd3@nifty.UUCP (Fabbian G. Dufoe, III) writes:
>> In article <107320004@hpfcso.FC.HP.COM> aoe@hpfcso.FC.HP.COM (Alexander Elkins) writes:
>>>There is a defect in SAS/C "se" (screen editor).  To see the defect turn
>>>on the auto-indent feature and turn off expand tabs to spaces.  Then type
>>>in exactly the following text test case, substituting keystrokes for <return>,
>>><tab>, and <backspace>:
>>>0123456789<return><tab>abcd<return><backspace>
>>>
>>>What you see is
>>>0123456789
>>>        abcd
>>>       89
>>>       ^cursor is here
>>>
>>
>>    It's not clear why you think this is defective behavior.  The cursor was
>> positioned at the beginning of the text on the previous line, less one space
>> for the backspace.  You could argue that the backspace should cancel the
>> <TAB> character.  It that what you think the program should do?
>>
>   This is exactly what it should do and is what it used to do!!
>Try the following as well.
><tab>012345<return>6
>
>What I see is the following
>       012345
>       612345
>       ^ cursor is here.
>
>What's going on here???  Does SAS know about this bug??
>I'm glad I expand tabs to spaces :-)

Yes, SAS is very much aware of this bug.  :-)

We're working on patches to all reported problems (just as we've always
done), but none are ready yet...

-- 
---------------
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: mks@cbmvax.commodore.com (Michael Sinz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: HDMem vs GigaMem for virtual memory on Amigas?
Date: 7 Oct 92 14:15:01 GMT
Article-I.D.: cbmvax.35632
Reply-To: mks@cbmvax.commodore.com (Michael Sinz)
Organization: Commodore, West Chester, PA

bjackson@mentor.cc.purdue.edu (Ben Jackson) writes:
>In article <35573@cbmvax.commodore.com> mks@cbmvax.commodore.com (Michael Sinz) writes:
>>chanson@nyx.cs.du.edu (Chris Hanson) writes:
>>>
>>[stuff about gigamem deleted]
>>>
>>>[stuff about 68EC040 deleted]
>>
>>So who started this falsism?  The A4000 has a *FULL* 68040 CPU in it!
>>A 68040 with *ALL* of the FPU functions of the 68040
>>A 68040 with *BOTH* of the MMUs that the 68040 CPU has
>>A 68040 that costs $800+ if you only buy one of them
>>
>>Now, I should know these things as I did the software that deals with
>>the 68040 on the A4000 (among other things) and it *uses* the MMU.
>>In fact, in every A4000 shipped, the MMU is turned on and actively in use!
>
>I was under the impression that the 68040 MMU was not capable of addressing
>partial maps (ie, map nothing or map the entire address space)  That would
>take a 2M map, if I recall correctly.  Of course, I was also under the
>impression that the '040 only had one MMU. :)  Whats the last word on '040
>MMU's?

The 68040 always had two MMUs...

The 68040 does not have early page termination.  This means that you have
to have the whole MMU table in some form.  With some rather tricky code
I was able to make it take rather little memory.  Also, as with the lower
levels of the 68030 MMU tables, the 68040 can have the MMU table itself
have parts of it in VM.  This can be used to make the MMU table not
really there all the time and just dynamically generate the areas that
are needed.  (VM in this case means that the complete table is not
all there and it will thus cause a fault and the requested page would
be built replacing an existing one, but this was not needed with my
trick, yet...)

/----------------------------------------------------------------------\
|      /// Michael Sinz  -  Senior Amiga Systems Engineer              |
|     ///                   Operating System Development Group         |
|    ///   BIX:  msinz      UUNET:  mks@cbmvax.commodore.com           |
|\\\///    "Can't I just bend one of the rules?" said the student.     |
| \XX/     The Master just looked back at him with a sad expression.   |
\----------------------------------------------------------------------/
From: bh00+@andrew.cmu.edu (Brian Hawkins)
Newsgroups: comp.sys.amiga.programmer
Subject: A4000 and Programming
Date: 12 Oct 92 17:31:48 GMT
Organization: Freshman, MCS general, Carnegie Mellon, Pittsburgh, PA

Hello all,

I own an Amiga 3000 and I am thinking of upgrading to an Amiga 4000. 
However I have a few questions concerning programming on the 4000 before
I decide.

1)  Can I still program it using the 2.0 includes for Aztec C?

2)  When will 3.0 includes and other stuff be available?

3)  Can the Haitex X-Specs3D glasses be used with the 4000?

4)  What are the input/output ports on the 4000?

5)  (This one is not really about programming)  How well do programs
written for 1.3 and 2.0 work?

Any other information A4000 in general or about programming would be
appreciated.  I don't always have time to read the bboard so if you can
send mail to bh00@andrew.cmu.edu I would appreciate it.  Thanks in
advance.

Brian Hawkins (bh00@andrew.cmu.edu)
From: barrett@astro.cs.umass.edu (Daniel Barrett)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Aztec C v5.2 argc bug
Date: 15 Oct 92 19:26:29 GMT
Reply-To: barrett@astro.cs.umass.edu (Daniel Barrett)
Organization: BLAZEMONGER INCORPORATED

In article <k74Qr*s51@caleb.UUCP> jdp@caleb.UUCP (Jim Pritchett) writes:
>Apparently, Aztec C v5.2 has a bug in it's argument passing for main().  If
>the last argument is "" (i.e. current directory), Aztec C will not count it
>as a valid argument.

	In an old version of Aztec, the command line parser would treat
quoted arguments like

		"foo bar"

incorrectly.  I suggest that you test your program with other arguments
in quotes -- for example, a file named "my file" or something like that --
and see if the problem is still there.

                                                        Dan

 //////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| Dan Barrett -- Dept of Computer Science, Lederle Graduate Research Center |
| University of Massachusetts, Amherst, MA  01003  --  barrett@cs.umass.edu |
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/////////////////////////////////////
Xref: sparky comp.sys.amiga.programmer:14440 comp.sys.amiga.applications:7867 comp.sys.amiga.misc:15099
From: doiron@starpt.UUCP (Glenn Doiron)
Newsgroups: comp.sys.amiga.programmer,comp.sys.amiga.applications,comp.sys.amiga.misc
Subject: Re:  HDMem vs GigaMem for virtual memory on Amigas?
Date: 12 Oct 92 02:22:02 GMT
 <dej.01pt@qpoint.ocunix.on.ca> <1992Oct4.192918.9506@ifi.unizh.ch>
Organization: 68K Software Development
X-NewsSoftware: GRn 1.16e (7/4/92) by Mike Schwartz & Michael B. Smith

In article <1992Oct4.192918.9506@ifi.unizh.ch> cschneid@avalon.physik.unizh.ch (Schneider Christian) writes:
> In article <dej.01pt@qpoint.ocunix.on.ca> dej@qpoint.ocunix.on.ca (David Jones) writes:
> >Does it work if I Forbid() and then page fault?  Disable() and page fault?
> >(i.e. if my Forbid() gets broken and whatever I was trying to mutex with
> >the Forbid() gets un-mutexed, then it don't work.)
> 
> GigaMem tries its best to keep Forbid()s mutex. This is nevertheless
> 100%, one could figure configurations where another task could sneak
> in and change some lists etc.
> Disable() does not work and will provoke a software failure-like requester
> giving the user the ability to Suspend/Reboot...
> 
> Note: Both this cases could be avoided for existing software due to
> GigaMem's unique feature to use program specific settings..
> Even for 'nasty' programs like ImageMaster which uses MEMF_PUBLIC for
> ALL his buffer allocations.

Oh, so now ImageMaster is nasty for following Commodore's guidelines for
programming?  I do believe that buffer memory is used by other processes...

Glenn Doiron
--
Amiga UUCP+
Origin:  uunet!starpt!doiron     (Organization:68K Software Development)
         BIX: gdoiron
** Not enough memory to perform requested operation.  Add 4 megs and retry.
From: aj639@cleveland.Freenet.Edu (Michael Cox)
Newsgroups: comp.sys.amiga.programmer
Subject: For AMOS Registered Users
Date: 11 Oct 1992 11:57:14 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: aj639@cleveland.Freenet.Edu (Michael Cox)
NNTP-Posting-Host: hela.ins.cwru.edu


I know a lot of people in the USA may not get the flyer from Europress
about how to upgrade to AMOS Pro, so here is the deal:

If you order by Oct 31, 1992, it is 30# + 4# shipping.  After Oct 31, 1992,
it is 35# + 4# shipping.  You must pay in pounds (#), and mail your cheque
or Internationa Postal Order to:

PO Box 2
Ellesmere Port
South Wirral
Cheshire L65 3EA
UK
You can also mail them your Visa/Mastercard number and signature.  If paying
by credit card, you can also call 51-357-1275 voice, or fax it to 51-357-2813.
It would be a good idea to send along your AMOS registration number if you
do not use the response letter they send you.  For a free demo disc, you
can call 625-859333.  They can also answer questions about the Compiler Pro.
The demo is also on wuarchive.wustl.edu and does work without 1 CHIP.

Mike
-- 
Okay, look for AmoNER Disk #4 on: (And, AMOS PRO is coming SOON!)
ux1.cso.uiuc.edu (128.174.5.59) in /amiga/amoner
nic.funet.fi (128.214.6.100) in /pub/amiga/programming/amos
From: heinz@edohwg.adsp.sub.org (Heinz Wrobel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  SAS/C 6.0 in Europe?
Date: 9 Oct 92 20:34:18 GMT
Organization: Edotronik GmbH

In article <Bvt0uD.J5v@unx.sas.com> walker@twix.unx.sas.com (Doug Walker) writes:
>
>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
>[...]
>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


Don't use the -4150, use the -4160. That's their international bureau. They
do the update stuff for the Amiga. Calling -4150 is useless as they tell
you to call -4160 ;-)

I called them because I feared that my upgrade order from _August_15th_ got
lost.  The person on the phone was helpful. Still, she couldn't find my
order. :-( She said, she was working her way through about _4000_ upgrade
orders for _all_ of Europe that they got from the US office. She said
they're sending upgrade notices right now as they get all that paper work
done sorted out. The pricing is a little different, though (read: more
expensive according to the current $ exchange rate in germany, IMHO). She
didn't know about a special discount for people who bought 5.10 after May,
1st. Another thing she said was that they are not really set up for credit
card orders yet. She said, they'd take it but it might take a little
longer. She didn't mention the possibility of COD orders and I got the
impression that the only way to go is: you order after you get your
upgrade notice, transfer the money via your bank (don't know the english
term for that) and then you get your upgrade. Pretty slow :-( If anybody
knows a faster way, please let me know. :-)

She took my address and compiler serial number again and I sure hope I get
my upgrade order form soon ... :-(

>=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =

--
Heinz Wrobel, Edotronik GmbH (ECG018)
FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
From: rtillery@crash.cts.com (Rick Tillery)
Subject: OpenScreenTags()...I'm confused
Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
Date: 11 Oct 92 18:52:05 PDT

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

As a result, at link time SAS does not know what to do about this function.
I've looked in the RKMs and there appears to be no noted difference between
this function and the others (other than the variable number of arguments
allowed), yet there is no obvious way to use it.

I'm obviously missing something obvious, but it beats the heck out of me
what that might be.
 
Any help (and a functional example of opening a screen (and maybe a window)
using OpenScreenTags() (and OpenWindowTags() which has the same problems))
would greatly be appreciated.
 
Rick Tillery
From: jk72+@andrew.cmu.edu (Jonathan Michael Kraly)
Newsgroups: comp.sys.amiga.programmer
Subject: 2.0includes
Date: 11 Oct 92 12:51:39 GMT
Article-I.D.: andrew.Ieq9DPa00WB=A8bHg3
Organization: Sophomore, Electrical and Computer Engineering, Carnegie Mellon, Pittsburgh, PA


	Are the 2.0 includes and libraries and things freely
distributable, is so are there any sites where they can be downloaded
from?
(jk72@andrew.cmu.edu)
From: koren@fc.hp.com (Steve Koren)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: more and System()
Date: 14 Oct 92 13:45:40 GMT
Article-I.D.: fc.Bw4685.Kw7
Organization: Hewlett-Packard Fort Collins Site
X-Newsreader: Tin 1.1.3 PL5

Michael B. Smith (mbs@adastra.cvl.va.us) wrote:
> 
> What are you setting SYS_Input to? SYS_Input is typically another filehandle
> instead of Input(), which is what System() defaults to. Setting that is
> probably not what you want to do.

Mike, thanks for the info.  More questions though:

Ok, why not?  I mean, I'm currently using SYS_Input to change the input
for everything that runs.  This works great for all programs I've tried
except for "more".  Similarly, I use SYS_Output to change the output.
For various reasons, by the time System() is called, it is impossible
for me to know the file name that the file handle is attached to - or at
least, it would place unacceptable restrictions on my program.

I'm confused about a few things now:

  * Why does SYS_Input work for everything else, but not "more"?  I
    always thought that, since you could redirect the input of "more",
    that it was somehow internally smart enough to get its user input
    from some other place such as an IDCMP port.

  * If I end up executing System("more < myfile"), doesn't that end up
    having the same effect?  Ie, more gets a different Input()?  If not,
    why is more a special case?  For other programs, running them and
    redirecting their input like that has the result of pointing their
    Input() someplace else.  Does this not also happen for more?  If it
    does, how is that any different than using SYS_Input?

  * If I am not willing to create a special case in my code for "more"
    by leaving SYS_Input alone, is there anything else I can do?

 - steve
Newsgroups: comp.sys.amiga.programmer
From: fisherc@bohra.cpg.oz.au (Craig Fisher)
Subject: Re: C++/G++ programming question
Organization: Computer Power Software
Date: Mon, 12 Oct 1992 04:55:59 GMT

In article <1992Oct8.011236.3156> paulg@tplrd.tpl.oz.au (Paul Gittings) writes:
> I've started using C++ (g++) as a "better C" and I've run into a problem.
> The definition for the graphics library pointer, GfxBase, in C is
>
>         struct GfxBase *GfxBase;
>
> or in C++
>
>         GfxBase *GfxBase;
>
> This works  OK and I can even assign a library pointer to GfxBase.
> The problem I run into is when I try to close the graphics library
>
>         CloseLibrary((Library*) GfxBase);
>
> I get a message from g++; name GfxBase could be a type or expression.
> Compiler assuming type.
> Which results in a parse error, because we really wanted the variable
> GfxBase not the type GfxBase.  Is there any way (I'm new to C++) to
> force the compiler to use the variable? or do I use another variable which
> is a reference to GfxBase?

I got around this problem by creating another variable and copying the
GfxBase value into it and using that to close the library. e.g.:

  struct GfxBase *GfxBase, *gb;

  GfxBase = OpenLibrary(....);
  :
  :
  gb = GfxBase;
  CloseLibrary(gb);

Not real neat, but it does get around the problem.

-Craig

-- 
=======================================================
| Craig Fisher                \ P.O. Box 686          |
| fisherc@bohra.cpg.oz.au      \ Woden, ACT 2606      |
| "Keep Yourself Alive" - Queen \ Canberra, Australia |