HDTenEightyP/NetNews huggingface dataset:
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: SAS C6
Originator: walker@twix.unx.sas.com
Date: Wed, 6 Jan 1993 14:10:20 GMT
Organization: SAS Institute Inc.


In article <SIE.93Jan6131614@introitus.fulcrum.co.uk>, sie@fulcrum.co.uk (Simon Raybould) writes:
|> 
|> Has anyone in the UK recieved update info from V5.10 to V6 yet?
|> 
|> I have stopped using SAS C as it doesn't work with the 68040 properly,
|> I am reliably informed that V6 works properly with the 40.

I am not aware of any problems with V5.10b and the 040.  Nor am I aware
of any problems with V6.0 and the 040.

|> I still haven't recieved any info about upgrading to V6.00, though
|> many people seem to be upgrading from V6.00 to V6.10 !!

No, not 6.10.  The latest version is 6.1.  The numbering scheme for 
6.x releases will be 6.1,6.2,...6.9,6.10,6.11, etc.  so 6.10 is very
different from 6.1.  Think of it as 6.1 = "Version 6, Revision 1",
6.10 = "Version 6, Revision 10".

|> It seems that new customers are getting precedence to V6.00 and us old
|> users are just getting left behind till last, a bit annoying that.

HiSoft should have sent upgrade letters in the UK.  If you haven't
received one, contact them and they will be able to handle your
upgrade.  You can also contact SAS Institute's German subsidiary
in Heidelberg, Germany and get an upgrade directly from them,
but if you do this, you won't be able to call HiSoft for support.

Old customers are NOT getting left behind.  UK customers should have
gotten letters at least a month ago.

|> Simon J Raybould    (sie@fulcrum.co.uk)               //              {o.o}

-- 
  *****
=*|_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: comeau@csanta.attmail.com (Greg Comeau)
Subject: Re: Wanted: info on available C++ compilers
Originator: comeau@well.sf.ca.us
Reply-To: comeau@csanta.attmail.com (Greg Comeau)
Organization: Comeau Computing
Date: Thu, 7 Jan 1993 15:01:13 GMT

In article <mbs.1jld@adastra.cvl.va.us> mbs@adastra.cvl.va.us (Michael B. Smith) writes:
>In article <C0H47o.JG8@well.sf.ca.us> comeau@csanta.attmail.com (Greg Comeau) writes:
>> In article <7cPfs*kI1@kink.PhaedraV.On.Ca> hugh@kink.PhaedraV.On.Ca (Hugh D. Gamble) writes:
>> >...You always have the
>> >option of getting the AT&T Cfront c++ front end from Comeau, which
>> >will be as good as the c compiler you put underneath it, but g++ is a
>> >top quality compiler.
>>
>> Neither of those latter two clauses are entirely accurate.
>
>Thanks for that wonderful, fact-filled, specific rebuttal Greg.        :)

Hey, any time ;-)  Seriously though, although the C compiler can be
considered as some sort of logical bottleneck or something given that
there is diversity of implementation and other issues in different C
compilers, to say that Comeau C++ is as good as the C compiler back
ended to it is simply not quite accurate.  Despite that we offer
so-called officially endorsed/testing/etc support for explicit C
compilers, quite a number of unofficial ones will work too.  This is
how and why lots of folks use Comeau C++ for embedded systems as well as
how Comeau C++ has come to be the most diversely ported commercial
C++ compiler anywhere.

Re g++, as the net continues to show, although gcc has finally reached
top quality status, g++ has not.  I feel that is an unbiased, accurate,
and representative statement.  And please: nobody take my statement out
of context!!  My statement is *NOT* that g++ is a piece of junk.
g++ has come pretty far just like Comeau C++ has.  We've has more than
our own share of weak moment in the past.  That's all another issue
than what my initial comment was though.

- Greg
-- 
         Comeau Computing, 91-34 120th Street, Richmond Hill, NY, 11418
                   Producers of Comeau C++ 3.0 With Templates
          Here:attmail.com!csanta!comeau / BIX:comeau / CIS:72331,3421
	    Voice:718-945-0009 / Fax:718-441-2310 / Prodigy: tshp50a
From: davids@cats.ucsc.edu (Dave Schreiber)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Flushing Devices; C= doco (mutter!)
Date: 8 Jan 1993 07:06:27 GMT
Organization: University of California; Santa Cruz
NNTP-Posting-Host: si.ucsc.edu


In article <crystal.726454269@glia> crystal@glia.biostr.washington.edu (Crystal) writes:
>In <1iia8tINNdeh@darkstar.UCSC.EDU> davids@cats.ucsc.edu (Dave Schreiber) writes:
>
>
>>In article <1993Jan7.092127.13752@philips.oz.au> gduncan@philips.oz.au (Gary Duncan) writes:
>>>Passing thought ; why the heck aren't unused libraries/devices
>>>flushed automatically anyway? Sounds like a legacy of the days 
>>>when hard disks were rare and dragging a device off floppy was
>>>time-consuming. Those days are gone...
>
>>Why should they be flushed?  An unused library essentially takes up
>>zero memory, since the memory it uses can be demanded from it at
>
>Then how come running "avail flush" returned 75k of memory to me if they
>take up ZERO memory...?

I said "_essentially_ takes up zero memory."  See below for the reason.

>
>>any time (and will be demanded from it before a memory allocation
>>is allowed to fail).  The only people for whom auto-removal of
>>libraries is important are developers who are checking for memory
>
>Warning: you are dealing in absolutes here... developers are not the ONLY
>people for whom auto-removal of libraries is important.  Those with
>little ram trying to run DTP programs or Database programs that access
>large textfiles or graphics likewise need to be able to have as much memory
>available to them as possible for their work, too.  

Reread what I said above.  If AllocMem() cannot allocate a block of memory
of requested size, it will flush all unused libraries and devices from
memory and try again.  A memory allocation _cannot_ fail because needed
memory is being occupied by a shared library or device.

>
>>leaks; there are plenty of ways of flushing libraries on those
>>rare occassions when it is needed.
>
>Ok, so, other than "avail flush", what other ways are there?  I want to
>recover as much as I can from those programs that don't clean up after
>themselves.

The following will work since the AllocMem() will always fail and thus
will always try and flush unused libraries and devices from memory
(unless, of course, the user has a chunk of memory 4G-16K large).

APTR *foo;
foo=AllocMem((unsigned long)(-16384),0L);

Also, if you run Workbench with the -debug option, you get a menu 
called "Debug" that contains an item called "flushlibs" that does
the same thing.

BTW, since the retaining of unused libraries in memory is an OS 
service, I'd hardly call it a case of programs "not cleaning up
after themselves."

>>>Gary Duncan			gduncan@rosella.pts.philips.oz.au	
>>Dave Schreiber  "Look.  Don't touch."  davids@cats.ucsc.edu (until 6/20/93)


-- 
Dave Schreiber  "Look.  Don't touch."  davids@cats.ucsc.edu (until 6/20/93)
Newsgroups: comp.sys.amiga.programmer
From: walker@twix.unx.sas.com (Doug Walker)
Subject: Re: How to get SAS/C 6.0 educational price
Originator: walker@twix.unx.sas.com
Date: Fri, 8 Jan 1993 14:43:13 GMT
Organization: SAS Institute Inc.


In article <C0HzsL.FAp@DMI.USherb.CA>, vailm00@DMI.USherb.CA (MARC VAILLANCOURT) writes:
|> Hi everybody,
|> 
|>    I'd like to have the information on how to get the special educational
|> pricing for SAS/C 6.0. I know they sell it for around 200$ US if you
|> can prove them you're a student, but I'd like to get all the details...
|>  
|>    Thanks in advance..
|> 
|> 	Marc
|> 

Send some kind of proof that you're a student or professor - 
perhaps a class schedule with your name on it, or a xerox of
a student ID - and $197.50 to the address below.

USA:

SAS Institute, Inc.
Book Sales
SAS Campus Drive
Cary, NC 27513
USA

Phone (919)677-8000
Fax   (919)677-8123

-- 
  *****
=*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 =
 *|. o.| ||                                          1200/2400/9600 Dual
  | o  |//     For all you do, this bug's for you!
  ====== 
usenet: walker@unx.sas.com                            bix: djwalker 
Any opinions expressed are mine, not those of SAS Institute, Inc.
From: fgd3@nifty.UUCP (Fabbian G. Dufoe, III)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  AllocRemember - how does it work?
Date: 4 Jan 93 03:06:44 EST
Distribution: world
Organization: Fabbian G. Dufoe, III

In article <1i5rpcINNj4j@agate.berkeley.edu> cliffwd@soda.berkeley.edu (Cliff Draper) writes:
>
>The AutoDocs describe this Intuition command.  But if your AutoDocs arn't
>handy....
>
>struct Remember  *remkey=NULL;
>
>char  *block1, *block2;
>
>if (!(block1=(char *) AllocRemember(&remkey, BLOCK1SIZE, MEMF_CLEAR)))
>   fail("insufficient memory");
>if (!(block2=(char *) AllocRemember(&remkey, BLOCK2SIZE, MEMF_CLEAR)))
>   fail("insufficient memory");
>/* use the 2 blocks as if you got them from AllocMem() */
>fail("all done");
>...
>/* and within fail() */
>FreeRemember(*remkey, TRUE);

   That'll cause you some problems.  It should be FreeRemember(&remkey,
TRUE) instead of "*remkey".

--Fabbian G. Dufoe, III
   350 Ling-A-Mor Terrace South   | GEnie:    F.DUFOE3
   St. Petersburg, Florida  33705 | internet: fgd3%nifty@tct.com
   813-823-2350                   | uucp:     ...tct!deep6!nifty!fgd3

Newsgroups: comp.sys.amiga.programmer
From: joel@dflores.eagle.mission.tx.us (Joel Garza)
Subject: Re: Multifinder for AmigaDOS (was Re: SpazEdit 2.1 for Amiga)
Date: Fri, 8 Jan 1993 00:30:13 GMT
Organization: Dave's Amiga

Seriously(?), how about something like THINK Reference?

It seems the multitasking would make this type of software reference
VERY nice, for programming.

JAGuar
From: lionet@lionfl.adsp.sub.org (Francois Lionet)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: AMOS - is it any good?
Date: 5 Jan 93 09:54:22 GMT
Reply-To: lionet@lionfl.adsp.sub.org (Francois Lionet)
Organization: Not an organization
X-Newsreader: Arn V1.00 alpha rel2

In article <1992Dec31.195211.11537@news.uiowa.edu>, Michael T Pins writes:

> The short answer is, no, it's not any good.
> I have yet to see a single AMOS program that doesn't have massive amounts of 
> Enforcer hits.  Considering the amount of AMOS programs that people have sent
> me, it would certainly indicate that the problem is with AMOS itself.

Well, sorry. I keep enforcer on with sushi on my system, and I can tell
you that the actual versions of AMOS does NOT produce ANY enforcer hit (1.34).
Of course the first versions of the langage did, mainly because of my
bad knowledge of the Amiga at first. Versions before 1.2 where absolutely
terrible for this.

The update for the very last version of AMOS are PD. Yes it means FREE.
You dont have to pay for them, and you can get them in any PD library.

What more can I do? I mean if people want to keep the old version, I cant
force them to get the new ones.
So I tell you, last version of AMOS, is 1.34, same for the compiler.
An update of AMOSPro (1.1) will be out in about 10 days, in PD as well.

By the way, I can tell you frankly, AMOS _is_ good ;-)

--
                    "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
From: kcd@cbmvax.commodore.com (Ken Dyke - Amiga Networking)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ResEdit 2.1 for Amiga
Date: 6 Jan 93 21:08:33 GMT
Reply-To: kcd@cbmvax.commodore.com (Ken Dyke - Amiga Networking)
Organization: Commodore, West Chester, PA

In article <C0F2Hn.86w@news.iastate.edu> barrett@iastate.edu (Marc N. Barrett) writes:
>In article <38338@cbmvax.commodore.com> kcd@cbmvax.commodore.com (Ken Dyke - Amiga Networking) writes:
>
>   Useless to someone with no imagination, perhaps.  I, however, would like to
>be able to take Amiga executable files apart and replace any imbedded images,
>sounds, etc.  If this is possible.

It's not that simple, unfortunately.

>> but of
>>course as usual you probably don't have a clue about how executables on the
>>Amiga actually work.
>
>   A veiled hint that it isn't possible.  I suspect that Amiga executable 
>files, despite being based on "chunks", are not as well-organized and
>structured as Mac executable files.  Meaning that there are no standardized
>methods of imbedding images, sounds, GUI structures, etc. in Amiga executable
>files.

You are confusing IFF Chunks with the "Hunks" that DOS uses in loadable files
for specifing code hunks, data hunks, and relocation information.  Any image
data used by an application is usually imbeded in the files data hunks (esp.
data required to be in chip ram).  However, DOS hunks don't specify what kind
of data is contained in data hunks, so editing image or sound data would be 
rather difficult.


-- 
Kenneth Dyke - Software Engineer            Internet: kcd@cbmvax.commodore.com 
Amiga Networking Group                      BIX: kcd     Phone: (215) 344-3014
"PPP?  You *must* be joking..."                      INCLUDE "stddisclaimer.i"
Newsgroups: comp.sys.amiga.programmer
From: jamie@cdevil.unx.sas.com (James Cooper)
Subject: Re: CPR under 1.3
Originator: jamie@cdevil.unx.sas.com
Date: Mon, 11 Jan 1993 16:22:44 GMT
Organization: SAS Institute Inc.


In article <8883@orbit.cts.com>, chucks@pnet51.orb.mn.org (Erik Funkenbusch) writes:
>
>I tried to load CPR to test some code under 1.3, for some reason, it tries to
>load icon.library (version 0) and fails.  icon.library doesn't show up on the
>resident list under 1.3, but does under 2.0.  There are no icon.libraries in
>my libs: directory on either the SAS or Workbench disks.  And there doesn't
>appear to be a 1.3 version of CPR.
>
>Is this a problem with the 6.1 CPR?

icon.library is a standard Commodore library, that has lived on the Workbench
disk in the libs directory for a long time (certainly since 1.3!).  You don't
say whether you installed to Floppy or HD.  If to HD, you must have deleted
icon.library at some point.  If to Floppy, I'll have to check the Install script
for the compiler... nope, its not automatically copied for you, so you will have
to copy it from your Workbench master to your SAS/C boot disk by hand.

If icon.library is not on your Master Workbench disk (the original you got from
Commodore), you must have deleted it yourself...

-- 
---------------
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: dstuve@storm.CS.ORST.EDU (David Stuve)
Newsgroups: comp.sys.amiga.programmer
Subject: FTXT & clipboard & SASC editor... Legal behavior?
Keywords: Subject says it all...
Date: 12 Jan 93 03:15:11 GMT
Organization: Computer Science Department, Oregon State University
NNTP-Posting-Host: storm.cs.orst.edu

I've noticed that SAS's 'se' (editor) seems to put 20 null
characters at the end of a section of text cut to the clipboard.
I've modified my pasting routine to ingore characters, but...
Is se's behavior correct?  Or should I file a bug report w/SAS?

-David.
-- 
========================================================================
David Stuve                          | InterNet: dstuve@storm.cs.orst.edu
Software Engineer                    |
MindWorks -- Advanced Amiga Software | Crescat Scientia Vita Excolatur
From: paulk@terapin.com (Paul Kienitz)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: More Amiga OS weaknesses and strengths
Date: 8 Jan 93 20:33:41 PST
Organization: BBS

> >   Another feature that is totally broken on the Amiga is
> > launching of applications by double-clicking a project.  On the
> > Macintosh, when you double-click a project, the 'creator'
> > application is always found and launched and the project is
> > loaded, no matter where the creator application is located on the
> > disk.  On the Amiga, tooltypes are almost always hard-coded.
> > There is almost no flexibility to the way the Amiga does it.
 
There is some flexibility, ONLY in the case when the tool in the
default tool field is given as a bare name with no path.  Most
existing icons have paths in the default tool field, either because
that's what apps write there or for 1.3 semi-compatibility.
 
> Not true.  I nearly always remove paths from tooltypes of icons I
> get from elsewhere.
 
You have to do that MANUALLY.  That is lame.
 
The WB needs stuff like: attempt the name without a path if the
pathed version does not exist, and check for a "FILETYPE=" tooltype
and use the user's preferred tool regardless of what the icon's
creator put there, if he has defined one for the filetype.  For
instance, any icon with FILETYPE=TEXT would go to (frinstance)
MuchMore, if you preferred that, instead of whatever viewer was
specified in the icon, and any FILETYPE=ILBM would go to (frinstance)
ViewTek instead of its own default tool.
 
What I do to get around this stuff is create appicons for a text
viewer and such with ToolManager, and when I see a text file icon I
just drop it there instead of double clicking, so I never have to
deal with someone else's choice of viewer.  I also have several
common viewer filenames all pointing to my preferred viewer.  Which
happens to be plain old C= More, used through my CLImax hack so it
gets its own public screen.
 
This is rather lame compared to the Finder.
 
> One problem with Mac icons, is that if you're doing development,
> and you have several versions of the application, you have to click
> on the application in order to guarantee you're using the right
> application.
 
Is the Workbench any better?
 
During development, I usually tell the linker to put the current
executable in RAM disk.  For some projects I put an icon there so I
can test the new executable with a WB launch.
 
If I double click it but the executable aint been linked yet, the WB
will find an app of the same name in my command path, and run that.
Mind you, this is a TOOL icon I'm talking about here, not a project
icon.  This "feature" once caused me to send a disk to a paying
customer that contained no executable copy of the program.  I thought
it was on the disk because when I double clicked it, another copy of
the program started up.
Newsgroups: comp.sys.amiga.programmer
From: dwmalone@maths.tcd.ie (David Malone)
Subject: Amiga an TEX
Summary: Has anyone written a TEX/DVI utility ?
Keywords: DVI TEX LATEX
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.
Date: Wed, 6 Jan 1993 18:22:35 GMT

I was wondering wether anyone out there had written a program 
for displaying TEX oduced DVI files on the amiga? If anyone 
has some code doing anything with these type of files I'd be
happy to canabalise is if they wouldn't mind.

	David Malone (dwmalone@maths.tcd.ie)
From: heinz@edohwg.adsp.sub.org (Heinz Wrobel)
Newsgroups: comp.sys.amiga.programmer
Subject: Re:  ETA for SAS 6.2?
Date: 11 Jan 93 18:51:20 GMT
Organization: Edotronik GmbH

In article <JRAJA.93Jan10164301@vipunen.hut.fi> jraja@vipunen.hut.fi (Jarno Tapio Rajahalme) writes:
>PS: Which is the preferred media for suggestions like this (news,
>main, emits)?

emits

>| Address: Jarno Rajahalme	       | EMail: 			     |

--
Heinz Wrobel, Edotronik GmbH (ECG018)
FAX +49 89 850 51 25 / TEL +49 89 850 25 20 (HOME!&VOICE, sometimes...)
From: ludde@dront.nada.kth.se (Erik Lundevall)
Subject: Re: Attn Commodore: You are making a Big Mistake (Hardware
Organization: Royal Institute of Technology, Stockholm, Sweden
Date: Mon, 11 Jan 1993 15:04:58 GMT

In <LZ21wB3w165w@lakes.trenton.sc.us> rock@lakes.trenton.sc.us (Rockerboy) writes:
>industry.  The logic of withholding the hardware manual does not wash.  
>The appropriate thing to do is demand responsibility from software 
>manufacturers.

Sure, that is what Commodores guidelines are for. Just look at the last
seven years for the results.

-- 
-Erik Lundevall             ludde@nada.kth.se           
                            ludde@adder.adsp.sub.org    
Your fault. Core dumped.

Newsgroups: comp.sys.amiga.programmer
From: ab@nova.cc.purdue.edu (Allen B)
Subject: How Fast Can The Serial Port Go?
Organization: Purdue University
Date: Mon, 4 Jan 1993 19:18:00 GMT

I would like to talk to my LaserWriter at a faster rate than
19.2Kb.  I know my (Fusion-Forty retrofitted 2000)
computer will go faster than that and that my (NTX)
printer will.  How fast can I get the UART or whatever to go?

And then, are there terminal programs that will let me go
that fast as well?  I mainly use my printer via a terminal
program now (interactive and ASCII file transfers) and
would be happy to stay that way.  (I'm a PostScript
programmer.)

(No the printer doesn't have a parallel port.)

Barring that, how bad is adding another (or several more)
serial port(s).  What are the user and programmer level
ramifications? 

ab
From: crystal@glia.biostr.washington.edu (Crystal)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Flushing Devices; C= doco (mutter!)
Date: 8 Jan 93 00:51:09 GMT
Article-I.D.: glia.crystal.726454269
Organization: University of Washington
NNTP-Posting-Host: glia.biostr.washington.edu

In <1iia8tINNdeh@darkstar.UCSC.EDU> davids@cats.ucsc.edu (Dave Schreiber) writes:


>In article <1993Jan7.092127.13752@philips.oz.au> gduncan@philips.oz.au (Gary Duncan) writes:
>>Passing thought ; why the heck aren't unused libraries/devices
>>flushed automatically anyway? Sounds like a legacy of the days 
>>when hard disks were rare and dragging a device off floppy was
>>time-consuming. Those days are gone...

>Why should they be flushed?  An unused library essentially takes up
>zero memory, since the memory it uses can be demanded from it at

Then how come running "avail flush" returned 75k of memory to me if they
take up ZERO memory...?

>any time (and will be demanded from it before a memory allocation
>is allowed to fail).  The only people for whom auto-removal of
>libraries is important are developers who are checking for memory

Warning: you are dealing in absolutes here... developers are not the ONLY
people for whom auto-removal of libraries is important.  Those with
little ram trying to run DTP programs or Database programs that access
large textfiles or graphics likewise need to be able to have as much memory
available to them as possible for their work, too.  

>leaks; there are plenty of ways of flushing libraries on those
>rare occassions when it is needed.

Ok, so, other than "avail flush", what other ways are there?  I want to
recover as much as I can from those programs that don't clean up after
themselves.

>I say this, BTW, as a non-professional developer with lots of hard
>drive space and RAM, and who was checking a program for memory leaks
>two days ago :-).

>>Gary Duncan			gduncan@rosella.pts.philips.oz.au	


>-- 
>Dave Schreiber  "Look.  Don't touch."  davids@cats.ucsc.edu (until 6/20/93)