HDTenEightyP/NetNews huggingface dataset:
From: dodd@mycenae.cchem.berkeley.edu (Lawrence R. Dodd)
Newsgroups: comp.lang.fortran
Subject: Re: Uglifier (was Re: Real Programmers)
Date: 17 Dec 92 04:20:04
Organization: Dept of Chemical Engineering, Polytechnic Univ, NY, USA
	<1992Dec17.102911.8075@newssrv.edvz.univie.ac.at>
NNTP-Posting-Host: mycenae.cchem.berkeley.edu
In-reply-to: pm@cc.univie.ac.at's message of Thu, 17 Dec 1992 10:29:11 GMT

>>>>> "Peter" == Peter Marksteiner <pm@cc.univie.ac.at> writes:

  Peter> Here's my favourite ugly program (uglified by hand, not by an automatic
  Peter> uglifier).

			   [much ugly code deleted]

  Peter> C  ... CALCULATE STARTING VALUES
  Peter> C
  Peter>       DO 10 I=Z-NDIF
  Peter>          C1 = 1.D0
  Peter> C        OOO0O(I)=SQRT(PI)*(I+1)/X(N)
  Peter> C        CALL REPLSR(OOO0O,O0OOO,NDIF,O,O0O0,OOO0O,C1)
  Peter>    10 CONTINUE        
  Peter>       IF(DABS(O).LT.1.E-15.AND.Z.GT.0.5) THEN
  Peter>           C=137.542
  Peter>           OOO0O=C
  Peter>      END IF

get rid of those indents. It makes it too easy to read.  Every should start at
column 7.
Newsgroups: comp.lang.fortran
From: danony@aix.rpi.edu (Yaron Danon)
Subject: Cile ompression /Decompression in FORTRAN 
Organization: Rensselaer Polytechnic Institute, Troy, NY
Distribution: comp
Date: Tue, 15 Dec 1992 19:25:29 GMT

Hello

I have a problem of transfering files between two computers over 
a serial line. The files are big and many and it takes alot of time.
I was thinking to compress the file on one computer and decompress
back on the other (which is a PC). The computer with the files is an
HP-1000 that has only FORTRAN on it.

Is there any FORTRAN source code for file compression avilable ??

Thanks,
Yaron 
Newsgroups: comp.lang.fortran
From: dil@mace.cc.purdue.edu (Perry G Ramsey)
Subject: Re: Uglifier (was Re: Real Programmers)
Organization: Purdue University, Department of Earth and Atmospheric Sciences
Date: Thu, 17 Dec 1992 14:38:31 GMT

In article <1992Dec17.102911.8075@newssrv.edvz.univie.ac.at> pm@cc.univie.ac.at (Peter Marksteiner) writes:
>Here's my favourite ugly program (uglified by hand, not by an automatic
>uglifier).
>...
What's this nonsense?

>      IF(DABS(O).LT.1.E-15.AND.Z.GT.0.5) THEN
>          C=137.542
>          OOO0O=C
>     END IF
>C

That should read


       IF(DABS(O).LT.1.E-15.AND.Z.GT.0.5) goto 409
410    continue
...
(elsewhere in the code)
409          C=137.542
          OOO0O=C
          goto 410

This helps clarify the code by not confusing the reader with the details
of what happens if (DABS(O) happens to be .LT.1.E-15.AND.Z happens to be
.GT.0.5).

Those writing uglifiers should remember this.
-- 
Perry G. Ramsey         Department of Earth and Atmospheric Sciences
dil@mace.cc.purdue.edu  Purdue University, West Lafayette, IN USA
perryr@purccvm          Life is short ...
N9LFF                   Don't waste it folding underwear.
From: jrbd@craycos.com (James Davies)
Newsgroups: comp.lang.fortran
Subject: Re: Uglifier (was Re: Real Programmers)
Keywords: n
Date: 16 Dec 92 16:43:47 GMT
Organization: Cray Computer Corporation

In article <BzC6n8.J2G@news.cso.uiuc.edu> ercolessi@uimrl3.mrl.uiuc.edu (furio ercolessi) writes:
>
>Hmmm ...
>did any one ever made a source code uglifier, a filter removing
>all comments, renaming all variables as A1,A2,... (*),  removing all
>extra spaces, replacing character constants with Holleriths, etc?
>It could be a useful tool after all!  Sometimes you do not want to
>give away your sources, you would like to give only the binaries
>but that's impractical ... this would be a brilliant intermediate 
>solution, give uglified code!  :-)

I once modified a prettyprinter I wrote to uglify instead (although I
didn't go so far as to rename variables).  Just removing the comments,
randomly indenting, and randomly inserting spaces and continuation-line
breaks has a remarkable negative effect on readability.  Unfortunately,
all of the things my obfuscator did (except for the comment removal)
were reversible by using the prettyprinter.

I've also used a simple C uglifier extensively for sending out proprietary 
source code in the past few years.  (I haven't yet seen any of it posted on 
the net, so it must be working. :-)  Of the two languages, obfuscated C
has a stronger resemblance to transmission-line noise than obfuscated Fortran,
probably because of all the curly braces...
Newsgroups: comp.lang.fortran
From: wilson@mailhost.aa.cad.slb.com (David Wilson)
Subject: F77 Standard
Organization: Schlumberger CAD/CAM; Ann Arbor, Michigan (USA)
Date: Thu, 17 Dec 1992 21:58:14 GMT

I would like to obtain a copy of the Fortran 77 Standard.  Does
anyone know where it's still available?

Dave Wilson


Newsgroups: comp.lang.fortran
From: lfini@sisifo (Luca Fini)
Subject: Re: F77 Standard
Organization: Osservatorio di Arcetri
X-Newsreader: TIN [version 1.1 PL6]
Date: Fri, 18 Dec 1992 08:22:37 GMT

David Wilson (wilson@mailhost.aa.cad.slb.com) wrote:
: I would like to obtain a copy of the Fortran 77 Standard.
: .....

You can obtain the F77 standard definition from:
American national Standard Institute, inc.
1430 Broadway, New York, NY 10018

The manual code is: ANSI X3.9-1978

Cheers,

+------------------------------------------------------------------------+
| Luca Fini                                                              |
| Osservatorio Astrofisico di Arcetri     Tel.   +55 2752 253            |
| L.go E.Fermi, 5                         Fax.:  +55 220039              |
| 50125 Firenze                           e-mail: lfini@arcetri.astro.it |
| Italia                                                                 |
+------------------------------------------------------------------------+
Newsgroups: comp.lang.fortran
From: shenkin@still3.chem.columbia.edu (Peter Shenkin)
Subject: Re: Dynamic Memory Allocation in FORTRAN, Question
Organization: Dept. of Chem, Columbia U, New York
Date: Sun, 20 Dec 1992 23:35:39 GMT
X-Posted-From: still3.chem.columbia.edu
NNTP-Posting-Host: sol.ctr.columbia.edu

In article <Dec.20.02.22.20.1992.7312@spade.rutgers.edu>
 xiong@spade.rutgers.edu (Xiong) writes:
>Hi, I am wondering if it is possible to allocate memory dynomically in
>FORTRAN as in C? 

No.


-- 
************************f*u*cn*rd*ths*u*cn*gt*a*gd*jb************************
Peter S. Shenkin, Box 768 Havemeyer Hall, Dept. of Chemistry, Columbia Univ.,
New York, NY  10027;  shenkin@still3.chem.columbia.edu;  (212) 854-5143
******* ...ghostlier demarcations, keener sounds.  (Wallace Stevens) ********
From: jrbd@craycos.com (James Davies)
Newsgroups: comp.lang.fortran
Subject: Re: Real Programmers
Date: 15 Dec 92 17:03:43 GMT
Organization: Cray Computer Corporation

In article <DODD.92Dec15053719@mycenae.cchem.berkeley.edu> dodd@roebling.poly.edu writes:
>
>>>>>> "Doctor" == Doctor FORTRAN <jsvrc@rc.rit.edu> writes:
>
>  Doctor>   101 Format (100 (' :-)'), /, ' For the Humor-impared.')
>  Doctor>       Write (Kout, 101)
>
> line 2: Error: attempt to use undefined variable "kout"
> line 2: Error: bad unit specifier type in write statement
> Compilation failed

Real FORTRAN programmers always write to unit 6, and then bitch
about the compiler being broken when it doesn't work.  
write(*,101) is for sissies :-)
From: sandee@vs11.scri.fsu.edu (Daan Sandee)
Newsgroups: comp.lang.fortran
Subject: Re: Real Programmers
Date: 16 Dec 92 17:02:17 GMT
Reply-To: sandee@vs11.scri.fsu.edu (Daan Sandee)
Organization: SCRI, Florida State University

In article <DODD.92Dec15142737@mycenae.cchem.berkeley.edu> dodd@roebling.poly.edu writes:
>
>Real FORTRAN programmers don't use lowercase letters, no excess space, no
>commas unless the compiler complains, and no unit number that can be
>remembered. so
>
> 85367 FORMAT(100(':-)')/'FOR THE HUMOR-IMPARED.')
>       WRITE(6,85367)

What's all these funny apostrophes ? Must be something wimpy they added
to the language after I learned it. Try
  85367 FORMAT(100(3H:-)X22HFOR THE HUMOR-IMPARED.)/)
Note the spelling, which indicates a Real Programmer.
Anyone want to find a compiler which still accepts this ? I know it's not
standard compliant, just customary.

Daan Sandee                                           sandee@scri.fsu.edu
Thinking Machines Corporation
Supercomputer Computations Research Institute, B-186
Florida State University, Tallahassee, FL 32306-4052  (904) 644-4490
From: shepard@sampson.ccsf.caltech.edu (Ron Shepard)
Newsgroups: comp.lang.fortran
Subject: Re: function name as an argument
Date: 15 Dec 1992 00:33:50 GMT
Organization: California Institute of Technology, Pasadena
NNTP-Posting-Host: sampson.ccsf.caltech.edu

I believe that the following is standard f77.  Note that the character
function is declared as (*) in the main program, and is declared, and
called, with different *(CONSTANT) values from the two subroutines.

It is apparently because of the requirement of *(CONSTANT) declaration
in the referencing subprogram that this can be done legally without
recourse to runtime memory allocation.

      program dumb
      character*30 cvar
      character*(*) cfun
      external cfun
      cvar='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
      call sub1( cvar, cfun )
      write(*,*) 'cvar=', cvar
      call sub2( cvar, cfun )
      write(*,*) 'cvar=', cvar
      stop
      end

      subroutine sub1( cvar, cfun )
      character*10 cvar
      character*10 cfun
c     # cfun() returns a 10-character value here.
      cvar = cfun()
      return
      end

      subroutine sub2( cvar, cfun )
      character*20 cvar
      character*20 cfun
c     # cfun() returns a 20-character value here.
      cvar = cfun()
      return
      end

      function cfun
      character*(*) cfun
c     # assign a 30-character value, truncating as necessary.
      cfun = '123456789012345678901234567890'
      return
      end

Upon execution on a couple of machines, I get:

cvar=1234567890xxxxxxxxxxxxxxxxxxxx
cvar=12345678901234567890xxxxxxxxxx

which is what I thought I should get according to the previous discussion
in this thread.  

Are there any machines that give different results?

-Ron Shepard
shepard@tcg.anl.gov
Newsgroups: comp.lang.fortran
From: tregilli@s21.msi.umn.edu (Ian Lee Tregillis [Astro])
Subject: Looking for random-number generator
Keywords: Random
Organization: University of Minnesota
Date: Mon, 14 Dec 1992 16:47:19 GMT

Greetings, 

	I'm not a regular reader of this group, 
but I did look in the FAQ before deciding to post
my request:

	I'm looking for a decent random-number 
generator in Fortran. (By 'decent' I mean one 
where a pseudo-random sequence won't repeat 
before at least 1000 samples.)  This is probably
something that real programmers learn to do before
age 10, but I'm obviously nothing of the sort.
Anyway, I'd appreciate it if anyone could give
me a hint or tell me where to look.

	Please respond by email to:
	tregilli@s1.msi.umn.edu
		or
	treg0001@student.tc.umn.edu

Many thanks in advance,
	Ian "Magnetic Moment" Tregillis
	Physics and Mathematics undergrad, U of MN, TC
Newsgroups: comp.lang.fortran
From: michael@chpc.utexas.edu (Michael Lemke)
Subject: Re: file redirection under unix
Organization: The University of Texas System - CHPC
Distribution: usa
Date: Tue, 15 Dec 92 20:23:53 GMT

In article <1992Dec15.192847.12970@wl.com> agrafiot@wl.com (Dimitris Agrafiotis) writes:
>
>A trivial question: how does one redirect fortran output on a unix system?
>(the vms equivalent would be DEFINE FOR012 file.dat). If the answer is
>soft links, how do we take care of multiple versions of the program 
>running in the same default directory?

In general, the answer is soft links.  However, there are Unixes around
that don't have soft links (Cray/UNICOS if I remember correctly) and
also some that have special commands to do what you want (e.g.
Cray/UNICOS' assign).

The version number problem is a nuisance but what can you expect from
Unix?  You have to create temporary directories.  Run the stuff in a
script (Bourne shell of course).  Here is my solution I use on a Sun. 
It should work on many systems:


#!/bin/sh
#
#	create temporary directory and define trap to make sure temp dir
#       is removed at job end
#
HERE=`pwd`
TEMP=$HOME/$$
mkdir $TEMP
trap 'cd ..; rm -r $TEMP; cd $HERE; exit' 0
trap 'echo -n "Clean up? " >&2
      read ans </dev/tty
      if [ ${ans}x != 'yx' -a ${ans}x != 'Yx' ]
      then
         echo "Ok, files left in" $TEMP >&2
         cd $HERE
         trap 0
      fi
      exit' 2
#
#	traps defined
#

#
#   Do the links here (also copy of input file if necessary); e.g.:
#
ln -s file.dat $TEMP/fort.12

#
# now switch to temp dir;  the reason I first copy files to $TEMP is that
#                          file.dat could have a relative path name
#
cd $TEMP

#
#  Do your stuff
#
stuff

#
# copy results back to where you started from.  Watch out again for 
# overwriting former results.  I love Unix.  

cp fort.7 ${HERE}/some_better_name_than_fort.7

#
# clean up is done by traps
#


If you have questions about this send me e-mail.

Michael
-- 
Michael Lemke
Astronomy, UT Austin, Texas
(michael@io.as.utexas.edu or UTSPAN::UTADNX::IO::MICHAEL [SPAN])
Newsgroups: comp.lang.fortran
From: julian@bjalon.demon.co.uk ("Julian Templeman")
Subject: Real Programmers) 
Distribution: world
Organization: Baker Jardine
Date: Wed, 16 Dec 1992 14:46:52 +0000


In article <BzC6n8.J2G@news.cso.uiuc.edu> ercolessi@uimrl3.mrl.uiuc.edu writes:

>
>In article <1992Dec16.025109.24541@coe.montana.edu>,> uesu03@giac1.oscs.montana.edu (Lou Glassy)
>writes:
>|>[...] Last year, an instructor
>|>handed out a small numeric code that followed all of the qualities
>|>listed by {Doctor FORTRAN| James|Laurence|Ian}.  No unnecessary spaces
>|>or commas, all caps, 98.7% of variables were 2 or 3 characters in
>|>length, and a whopping 5 comments in about 1500 lines of source.
>|>Blecch!
>
>Hmmm ...
>did any one ever made a source code uglifier, a filter removing
>all comments, renaming all variables as A1,A2,... (*),  removing all
>extra spaces, replacing character constants with Holleriths, etc?
>It could be a useful tool after all!  Sometimes you do not want to
>give away your sources, you would like to give only the binaries
>but that's impractical ... this would be a brilliant intermediate 
>solution, give uglified code!  :-)
>--
>Furio Ercolessi
>Materials Research Laboratory           |   Intl School for Advanced Studies
>Univ. of Illinois at Urbana-Champaign   |   Trieste, Italy
>furio@uiuc.edu                          |   furio@sissa.it

Don't laugh - a company I used to work for actually used this system. They
had a program for 'camouflaging' the source of their Fluid Dynamics program, 
which did all the things you suggested, and for much the same reasons. 

They supported the code on a *lot* of machines (when I was there in '86 or 
'87, there were several dozen), and since we didn't have easy access to some
of them (like Crays, and some of the Cyber supercomputers), the shrouded
source used to get sent out instead. 

And *guess* who used to get sent out to get it running when problems arose?
Ever tried debugging uglified code? I used to have a huge printout giving
the mapping between real and fake variable names.....

I still remeber the time when the Chairman (in the US, read 'CEO')  met one 
of his old university buddies at a conference, and told us to give him a 
plain-text version. Turned out he was a consultant for a major competitor. 
Ho-hum.

Ah, those were the days.

julian,
who used to work
for CHAM
in london
Newsgroups: comp.lang.fortran
From: fairfield@slacvx.slac.stanford.edu
Subject: Re^2: Help With Named common blocks...again
Organization: Stanford Linear Accelerator Center
Distribution: comp
Date: Wed, 16 Dec 1992 04:49:35 GMT

Thanks, Michael, for prviding the additional information:

In article <jumper.724475994@garfield.catt.ncsu.edu>, jumper@garfield.catt.ncsu.edu (Michael Lanham) writes:
[...]
> Now I find in a file separate from the data file (the first one to declare what
> SHARE1 is like) a use of SHARE1 entirely different.  This is in the first
> SUBROUTINE in this src file that uses SHARE1 and every other routine that uses
> SHARE1 in this file also follows the convention below. 

[...]

> My original question still stands.  Since these declarations are not the same
> length nor (obviously) the same size arrays, is the second set of definitions
> concatenated to the first?  Or, because they are in separate files, and
> because in the second file(the odd man out file) the first declaration of
> SHARE1 is _not_ like the datafile definition, they are pointing to the same
> address space(ie TABLE(1) = NSVT(1) and OSVT(1) = TABLE(1001)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    This latter is the case (evidently I was correct in my original 
followup...just lucky I guess :-).  Since the named common appears only
once in each program section, the second varient you encountered refers
to the same storage locations as the first varient, but with different
names and, possibly, data types.  That is, it is as if the second version 
were a alternative MAP within a UNION.  To the extent you can, verify that
this is the intended behaviour.

	-Ken
-- 
 Dr. Kenneth H. Fairfield    |  Internet: Fairfield@Slac.Stanford.Edu
 SLAC, P.O.Box 4349, MS 98   |  DECnet:   45537::FAIRFIELD (45537=SLACVX)
 Stanford, CA   94309        |  BITNET    Fairfield@Slacvx
 ----------------------------------------------------------------------------
 These opinions are mine, not SLAC's, Stanford's, nor the DOE's...
Newsgroups: comp.lang.fortran
From: dafnioti@cae.wisc.edu (Petros Dafniotis)
Subject: Re: Linking Borland C w/ Lahey Fortran possible?
Organization: U of Wisconsin-Madison College of Engineering
Date: 15 Dec 92 10:53:46 CST

In article <92350.163016IFF291@DJUKFA11.BITNET> IFF291@DJUKFA11.BITNET (Stephan Petersen) writes:
>
>Hi there,
>
>does anybody by chance know whether Lahey F77L - Fortran V4.0.2 (MS-DOS)
>object code can be linked with Borland C++ object code? If not, which
>other MS-DOS C-compiler does allow for it?
>
  The Lahey manuals claim that you can link with TC v1.5 object files.
I do not know anything else.


					Petros Dafniotis
					Chem Engr Dept, UW-Madison
				e-mail:	dafnioti@cae.wisc.edu
From: khb@chiba.Eng.Sun.COM (Keith Bierman fpgoup)
Newsgroups: comp.lang.fortran
Subject: SunPro f90 plans made public
Date: 17 Dec 92 02:25:31 GMT
Organization: SunPro
NNTP-Posting-Host: chiba


Complete text of the press release available upon request:

SUNPRO ANNOUNCES FORTRAN 90 TECHNOLOGY AGREEMENT WITH THE NUMERICAL
ALGORITHMS GROUP, LTD.
 
MOUNTAIN VIEW, Calif - December 15, 1992 - SunPro(tm), the software
development business of Sun Microsystems, Inc., today announced that
it has entered into a technology development and licensing agreement
with The Numerical Algorithms Group, Ltd (NAG(TM)). The agreement
centers on NAG's Fortran 90 technology. ....to develop and market a
high performance Fortran 90 development system based on SunPro's
proven SPARCompiler and SPARCworks(tm) development environment
technologies.
 
SunPro will enhance NAG's technology and combine it with their own high
performace compiler technology to create an integrated Fortran 90
language system ....

While we certainly have no objection to someone else posting the
entire press release, I prefer to not presume too much on the net's
patience ;>
--
----------------------------------------------------------------
Keith H. Bierman    keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM
SunPro 2550 Garcia MTV 12-40             | (415 336 2648) fax 964 0946
Mountain View, CA 94043  <speaking for myself, not Sun*> Copyright 1992
Newsgroups: comp.lang.fortran
From: moniot@dsm.dsm.fordham.edu (Robert Moniot)
Subject: Re: Help With Named common blocks...again
Organization: Fordham University/CLC, Division of Science and Math
Distribution: comp
Date: Wed, 16 Dec 1992 17:02:47 GMT

In article <jumper.724475994@garfield.catt.ncsu.edu>
jumper@garfield.catt.ncsu.edu (Michael Lanham) writes:


> Let me start over.  I have a program that has several source files.  The data
> module consists entirely of a BLOCK DATA segment.

> In that data module there is a COMMON block that looks like the following.

   [stuff omitted]


> Now I find in a file separate from the data file (the first one to declare what
> SHARE1 is like) a use of SHARE1 entirely different.

Someone may already have said this in a reply, but if so I missed it:

The example given is not standard conforming because the block
declarations are of different lengths.  Section 8.3.3 says "Within an
executable program, all named common blocks that have the same name
must be the same size."

This rule does not apply to blank common, which is probably why many
people don't remember that it does apply to named common.

Also, some of the variables in the common blocks had names like
CHAR(n).  If there were accompanying declarations (not shown)
declaring these variables to be of type CHARACTER, then the example is
also not standard conforming due to mixing character and numeric types
in the same block.   See Section 8.3.1.



--


Bob Moniot
Fordham University
College at Lincoln Center
New York, NY  10023  (212) 636-6331

BitNet:   MONIOT@FORDMULC
InterNet: moniot@mary.fordham.edu
From: ray@philmtl.philips.ca (Ray Dunn)
Newsgroups: comp.lang.c
Subject: Re: Peek/Poke in C
Date: 20 Dec 92 01:16:45 GMT
Organization: Not Philips.

In refd article, behrenss@Informatik.TU-Muenchen.DE (Soenke Behrens) writes:
>>ericwebb@blackwlf.gwinnett.com (eric webb) writes:
>>>Hi again.. does anyone know how to do equivalent of BASIC's PEEK & POKE
>>>statements in C?
>
>Very implentation-specific. Some architectures allow something along
>the lines of
>
>char *address;
>
>address = 0x678090;
>*address = 80; /* poke $678090,80 */
>printf ("And peek gives us: %d\n",*address);

_All_ architectures allow the above constructions.  What is architecture
specific is the range of numeric addresses which are meaningful, and
whether the addresses are absolute or relative to some base or segment
start address.  This is actually no different from PEEK and POKE in the
general case.

There are even architectures in which you can address _registers_ in this
way, and of course if running on hardware that has memory mapped I/O, the
I/O ports can be accessed using the same technique too.

On the PC you can create an absolute memory address so long as you define
the pointer to be of type far.  If you don't, then in small or medium model
the address is taken to be relative to the start of the data segment.  Far
pointers can be created into other segments by using (in MSC) the FP_SEG
and FP_OFF macros.
-- 
Ray Dunn at home        |  Beaconsfield, Quebec  |  Phone: (514) 630 3749
ray@philmtl.philips.ca  |  ray@cam.org           |  uunet!sobeco!philmtl!ray
Newsgroups: comp.lang.c
From: rfries@sceng.ub.com (Robert Fries)
Subject: Re: Question to test general C knowledge
Organization: Ungermann Bass
Date: Thu, 17 Dec 1992 23:47:19 GMT

In article <rfries.150@sceng.ub.com> rfries@sceng.ub.com (Robert Fries) writes:

>In article <1992Dec16.231449.22903@cs.uow.edu.au> davidr@cs.uow.edu.au (David Ian Raymond) writes:

>>d_north@ondec.lonestar.org (David G. North, CCP) writes:

>>>Or better yet, what is the type and value of the following expression:
>>>  "this is a test"[4]

>>I give up. What is it?

>The value is ' '. 
>An even more bizarre way of writing it is:
>       4["this is a test"]

Oops, as someone pointed out to me, I forgot to mention that the type
is char, so the value is more precisely (char)' ' , since ' ' is an int.

Robert

//////////////////////////////////////////////////////////////////////////
Robert Fries
Ungermann-Bass Inc.

DISCLAIMER:
    Opinions contained herein are my own, and are not necessarily those
    of Ungermann-Bass.
//////////////////////////////////////////////////////////////////////////
Newsgroups: comp.lang.c
From: gjkirk@napier.uwaterloo.ca (Gerald Kirk)
Subject: Purchasing C
Organization: University of Waterloo
Date: Sat, 12 Dec 1992 17:14:26 GMT

I am looking at possibly purchasing a C compiler.
I would like something that has a debugger and a
decent library, but that does not cost hundreds
of dollars.

Does anyone have any suggestions?