HDTenEightyP/NetNews huggingface dataset:
From: bnixon@fnma.com (Bill Nixon)
Subject: Re: instance variable declarations..
Organization: FannieMae, Washington, DC
Date: Thu, 3 Sep 1992 02:03:52 GMT

Just my two cents:

It seems to me that declaring instance variables in an object's
interface file somewhat breaks the idea of encapsulation and
abstraction that object-oriented languages should provide.

What I have seen done in other language specifications, most recently
OS/2 SOM, is to provide three interface files (.h) for an object:

+ public - which has all public instance variables and methods.
Everything defined in this file is directly accessible, even instance
variables.  This and the "compiled" code for the object is all an
object user needs to have.

+ private - which has all private instance variables and methods.
All instance variables and methods declared in this file are limited
in scope and cannot be directly accessed.  (Normally this is also
the source file which contains all the code for the methods).

+ class - which has all instance variables and methods which can
be modified via inheritance.  An object subclasser would require
this file along with the "compiled" code in order to write a subclass of
the object.

I am more comfortable living in a private and public environment.
Basically only put "need to know" data (methods and maybe a few
instance variables) in the public interface file.  Since most instance
variables should be private to provide true data abstraction, they would
not be exposed and this may provide a simplier and "safer" view of the
object.

Bill
-- 
email: bnixon@fnma.com (NeXT Mail Okay)
Bill Nixon, Senior Programmer Analyst, Advanced Technology
FannieMae, 3900 Wisconsin Ave NW, Washington, DC 22016     (202) 752-5468
Newsgroups: comp.lang.objective-c,comp.lang.c++
From: kocks@jessica.stanford.edu (Peter Kocks)
Subject: Re: Objective-C vs. C++
Organization: Academic Information Resources
Date: Wed, 2 Sep 92 20:34:08 GMT


In article <1992Aug25.142415.7762@uc.msc.edu>, andy@uh.msc.edu (Andrew
Hollenbeck) says:

>I've used C++ and would like to know what distinguishes Objective-C from C++.
>The Objective-C FAQ (Q6/A6) only indicates features that C++ contains that
>Objective-C lacks.  What features of Objective-C make it "better"?
>

LATE BINDING!!! is one very important feature of Obj-C, which is not
defined in C++.  In C++ you must do late binding on the os level (like
resource forks on the Mac) or extend the language for a particular
compiler (like the DDL libraries of MS). 

Why is this so important?  Because a truly object oriented working
environment (eg one where objects can be added or subtracted by the
user of an application) requires that the application not know all the
detials of the objects used by the appilcation before compiling.  MS
gets around this problem with DDL libraries, but this only works for
systems and compilers which can use those libraries.  Obj-C does late
binding by default.  You can write an application in Obj-C and make
use of late binding and then bring it to another os and recompile and
still have late binding.  If you use C++ you will have to do a lot
more tailoring to the native os.  

This may seem like a somewhat minor point, but I think it extremely
important.  As user environments become more and more object oriented,
it will be increasingly important to develop custom objects.  In C++
you will have to write the object and then either relink the
application or use something like a DDL library.  If you do the later,
as I suspect many people will do.  Then when you go to a Mac you will
have to completely rewrite the object again.  If you had used Obj-C
you may need to make some minor modifications, but going between
enviroments would be comparatively easy.

--Peter Kocks
  kocks@chemistry.stanford.edu
From: alex@cs.umd.edu (Alex Blakemore)
Newsgroups: comp.lang.objective-c
Subject: Re: Objective C library, Free Software Foundation
Date: 4 Sep 92 18:06:29 GMT
Distribution: usa
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742

> :  NeXT smokes  
> : everyone when it comes to the GUI classes, but is sorely lacking when it comes  
> : to data modeling classes (i.e. Set, Bag, SequenceableCollection, Collection,  

well there are classes from other sources than NeXT.
check out the Object Catalog form NeXT - its well worth $10
(1-800-Try-NeXT)

there are lots of classes listed including ...

for foundation classes, you can get StepStone's ICpak for only $145
20 classes, 300 methods for basic data structures - claimed to
be flexible and extendible - I havent used them (yet)

(203)426-1875
hotline@stepstone.com
-- 
---------------------------------------------------
Alex Blakemore alex@cs.umd.edu   NeXT mail accepted
Newsgroups: comp.lang.objective-c,gnu.misc.discuss
From: wiml@milton.u.washington.edu (William Lewis)
Subject: Re: PD Implementation?
Organization: University of Washington, Seattle
Date: Thu, 27 Aug 1992 05:11:42 GMT

In article <1992Aug19.081740.10359@nevada.edu> oliverm@nevada.edu (Moises Oliveira ) writes:
>In an article in (comp.lang.objective-C) khera@cs.duke.edu wites:
>>yes, and it is totally useless until someone writes the runtime
>>message dispatching routines.  basically, it doesn't have an Object
>>class.
>
>Is GNU working on the runtime support for Objective-C?  Is someone
>doing it and planning on donating it to GNU?  Is GNU Objective-C
>still born? or will it one day get some life?

  My understanding is that Cygnus (Your GNU Support) is working on
it. But this is a pretty old impression and I've seen nothing actually
come of it. (For all I know it'll be announced tomorrow, though.)

  I'm waiting for GNU-ObjC to appear so I can duplicate the NeXTstep
programming environment for X. With, of course, a few changes
in the hierarchy. (BTW, if anyone else is also thinking of this,
I'd be interested in exchanging ideas with you via email... there
are a few things in NS that I really think could be improved in 
a ground-up rewrite.)

-- 
email: wiml@u.washington.edu             |  Home:  Seattle, Washington   |
     (William Lewis)                     |  47 41' 15" N   122 42' 58" W | 
NeXTmail: wiml@ingalls.cs.washington.edu `-------------------------------'
        --*-- Member, Coalition to Preserve Semantic Vacuity --*--
From: lerman@seltd.UUCP (Kenneth Lerman)
Newsgroups: comp.lang.objective-c
Subject: Re: Objective-C vs. C++
Date: 29 Aug 92 14:42:36 GMT
Reply-To: lerman@seltd.UUCP (Kenneth Lerman)
Organization: Systems Essentials Limited

In article <1992Aug28.182704.10020@cs.mcgill.ca> samurai@uriel.cs.mgill.ca writes:
...referring to type checking...
>Isn't ANSI C pretty strong about this? I know gcc2.2.2 drives me
>WILD with warnings :-). And Objective C (well, NeXT's anyway)
>is ANSI.
...

Recall that Stepstone's compiler is a precompiler which generates C
code as output.

Stepstone's Objective-C compiler accepts ANSI C and generates ANSI or
K&R variants depending on whether it is used with ANSI or K&R
compilers.  It will do type checking of messages to objects whose
types are statically defined, e.g.:

    Foo *aFoo;
    ...
    [aFoo blech];

will verify that objects of type Foo respond to the blech message.  A
diagnostic will be generated if it does not.

One objection to runtime dispatching of messages which is often made
by the C++ advocates is that you may get "doesNotRecognize" errors
during runtime if your code is not statically checked by the compiler.
My answer to this is:
  You mean you don't test your code?

It has been my experience that doesNotRecognize errors are generally
easy to find and fix.

That is in contrast to the correction of memory leaks and messages to
freed objects.  The former is easy to detect and often very hard to
understand and fix.  The latter is usually easily detected by the
Objective-C runtime, but is sometimes very hard to detect and may take
days to understand and fix.


-- 
Kenneth Lerman                  ...!uunet!casey!gaboon!seltd!lerman
Systems Essentials Limited                            (203)426-4430
55 Main Street
Newtown, CT 06470
Newsgroups: comp.lang.objective-c,comp.lang.c++
From: andy@research.canon.oz.au (Andy Newman)
Subject: Re: Objective-C vs. C++
Organization: Canon Information Systems Research Australia
Date: Wed, 26 Aug 1992 06:18:03 GMT

andy@uh.msc.edu (Andrew Hollenbeck) writes:
>I've used C++ and would like to know what distinguishes Objective-C from C++.
>The Objective-C FAQ (Q6/A6) only indicates features that C++ contains that
>Objective-C lacks.  What features of Objective-C make it "better"?
You answered your own question. The things about Objective-C that make
it better than C++ are all the features that C++ has that Objective-C
doesn't. NeXT, though, seem to be fixing that ;-)

>C++ is certainly more popular, but that doesn't necessarily mean that it is
>better.
Precisely.

>Thanks,
>-- Andy
That's fine,
-- Andy
-- 
Andy Newman (andy@research.canon.oz.au)		"int - God's own type"
Xref: sparky comp.lang.objective-c:477 comp.lang.c++:12916
From: johnw@bobcat.cbm.commodore.com (John F. Wiederhirn)
Newsgroups: comp.lang.objective-c,comp.lang.c++
Subject: Re: Objective-C vs. C++
Date: 26 Aug 92 15:44:36 GMT
Organization: Commodore Applications and Technical Support

timm@void.ncsa.uiuc.edu (Tim McClarren) writes:
> andy@uh.msc.edu (Andrew Hollenbeck) writes:
> >C++ is certainly more popular, but that doesn't necessarily mean that it is
> >better.  You can walk into any bookstore and find a couple dozen C++ books, but I
> >have yet to find a single Objective-C book in those stores.
> 
> There aren't any decent Objective books...don't waste your money on
> the Weiner and Pinson book.  It's terrible.

The seminal work by Brad Cox and Andrew Novobilski is quite good, IMO.
It's rather readable, and explains quite a bit about OOLs in general,
Objective-C in particular, and the Objective-C compiler framework in
detail.
-- 
==========================================================================
       John Wiederhirn - Commodore Applications & Technical Support
         {uunet,rutgers}!cbmvax!johnw  johnw@cbmvax.commodore.com
Newsgroups: comp.lang.objective-c
From: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
Subject: Re: Objective-C vs. C++
Reply-To: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
Organization: California Institute of Technology, Pasadena
Distribution: usa
Date: Fri, 28 Aug 1992 18:47:25 GMT

In article <timm.715023052@void> timm@void.ncsa.uiuc.edu (Tim McClarren)  
writes:
> pfkeb@kaon.SLAC.Stanford.EDU (Paul Kunz) writes:
> >   It is easy to conceive of an application that has a C++ computation
> >kernal with an Objective-C GUI.  All you need is the ultimate
> >language: Objective-C++.  What is Objective-C++?  Well if Objective-C
> >is a layer on top of C, the Objective-C++ is a layer on top of C++.
> >And it is available today from your GNU sources or any NeXT machine.
> 
> Uh, not quite.  I wouldn't term what the GNU compile supplied with
> the NeXT does as Objective-C++.  The two don't mix as freely as you're
> implying.

Well, it is true that you cannot send Objective-C messages to C++ classes.  But  
Paul's statement is true as it stands.  Objective-<blatz> means adding a couple  
new data types and messaging syntax to an existing language.  Thus, Objective-C  
add those things to C, Objective-FORTRAN (yes, it exists on the NeXT) adds  
those constructs to FORTRAN, and Objective-C++ adds those constructs to C++.  

Paul's point was that the 'Objective-' layer could sit directly on top of  
another language without any problem.  They are distinct, but cooperative and  
complementary.  Using them in that manner is very easy and natural, and I've  
done several software projects that way, and hope to do more in the future.   
True, it is a "layering", not a "mixing", but I don't consider that a  
disadvantage.

Perhaps you want to use the term Objective-C++ to for a language where you have  
a single concept of Class which can be messaged using either C++ or  
"Objective-" syntax.  I think such a thing would be difficult to define,  
painful to implement, confusing to use, and probably not very useful.   
Therefore, I claim Paul's use of the term Objective-C++ is the 'correct' one  
(in the sense of being well-defined and  useful).

- Ernie P.
Disclaimer:  Paul is a friend of mine, and us computational physicists need to  
stick together. :-)
--
Ernest N. Prabhakar                  Caltech High Energy Physics
Member, League for Programming Freedom (league@prep.ai.mit.edu)
CaJUN President        NeXTMail:ernest@pundit.cithep.caltech.edu
"...and ourselves, your servants for Jesus sake." - II Cor 4:5b
#import <std/disclaimer.h>
Newsgroups: comp.lang.postscript
From: grover@mighty-joe.isri.unlv.edu (Kevin Grover)
Subject: Re: Help requested from postscript *Gurus* 
Reply-To: grover@isri.unlv.edu
Organization: Information Science Research Institute (UNLV-ISRI)
Date: Wed, 26 Aug 92 19:26:55 GMT

In article <1992Aug26.180305.1406@unlv.edu>, grover@mighty-joe.isri.unlv.edu (Kevin Grover) writes:

) /showpage {
)   Tdict begin
)   /pgcount pgcount 1 add def		% Bump page count by 1
)   pgcount LASTPG ge {
) 	oldshowpage
)   } if
)   end
) 
)   % NEED CODE HERE TO POSSITION NEXT PAGE
) }

Opps, make that last line

} bind def

--------------------------------------------------------------------------
 Kevin O. Grover      | UNLV Computer Science and Electrical Engineering
 grover@isri.unlv.edu | ISRI - Information Science Research Institute
 CServe: [73627,1677] | 4505 S. Maryland Parkway, Las Vegas NV 89154-1017
From: andy@ice.stx.com (Andy Moore)
Newsgroups: comp.lang.postscript
Subject: Readers Digest Condensed Summary of Postscript?
Keywords: postscript, novice, wishful thinking
Date: 4 Sep 92 15:03:09 GMT
Reply-To: andy@ian.stx.com
Organization: Hughes STX, Lanham, MD

Howdy, and forgive me if this is a FAQ (which I've been watching for; can
anybody point me to one to ftp?), or worse yet, an unrealistic request:

Has anyone got a brief overview of Postscript handy?  Yes, I'm looking
for a good book for a more complete study (any recommendations?), and
NO, I don't expect to be able to gain a full working knowledge from 
self study, trial and error, and the kindness of strangers.  But I've
gleened some aspects of it just by looking at LOTS of example Postscript,
and I'm *almost* brave enough to dive in and try some...

Just seems to me that Postscript is logical and consistent enough that
you could express a basic survival summary of it in a page or two...
If not, don't flame me, just explain in your least condensending tone
why Postscript is just too involved or dangerous to summarize...

Would I, could I, attempt to summarize Pascal or C in such a way?  Sure!
(Maybe in this case Forth would be a better example, eh?)
Thanks in advance and take care...
______________________________________________________________________________
Andy Moore         "You keep your dream, and I'll keep the money!"
 andy@ice.stx.com                      - Ren Hoek, "The Ren and Stimpy Show"
Xref: sparky comp.lang.postscript:4580 comp.sys.sun.wanted:1403
From: IFF291@DJUKFA11.BITNET (Stephan Petersen)
Newsgroups: comp.lang.postscript,comp.sys.sun.wanted
Subject: WANTED: Type-1 -> F3 font conversion util.
Date: 4 Sep 92 12:45:25 GMT
Organization: Forschungszentrum Juelich


Does anybody know of a utility that can convert Type-1
fonts to the F3 format?


Thanks for any pointers!

Stephan


+------------------------------------------------+
| Stephan Petersen                               |
|                                                |
| Bitnet/EARN: IFF291@DJUKFA11                   |
| Internet:    IFF291@zam001.zam.kfa-juelich.de  |
+------------------------------------------------+
From: ziehmer@aix4.rhrk.uni-kl.de (Thomas Ziehmer [E-Technik])
Subject: Print JPEG-Files with PS
Reply-To: ziehmer@aix4.rhrk.uni-kl.de (Thomas Ziehmer [E-Technik])
Organization: rhrk
Date: Thu, 27 Aug 1992 21:03:55 GMT

We have an Tektronix Phaser III Sublimation-printer and we want to print
JPEG-files. The problem is that we need an header PostScriptfile to do so.
Can anyone give us an solution or an tip what the correct headerfile is.
An other question is, can we print JPEG-files which where compressed with
the PD-cjpeg from the Independent JPEG Group?

  Bye
     Thomas Ziehmer
---
 Thomas Ziehmer                     | phone   049-631-205-2154
 Regionales Hochschulrechenzentrum  | privat  049-6301-4831
 Kaiserslautern                     | 
                                    | email   ziehmer@rhrk.uni-kl.de
 6750 Kaiserslautern                |
 Germany                            |
From: wiedeman@uci.edu (Lyle Wiedeman)
Subject: reporting error conditions
Newsgroups: comp.lang.postscript
Organization: University of California, Irvine
Date: 4 Sep 92 16:22:55 GMT
Distribution: usa

Greetings,

I understand there exists a snippet of Postscript code which, when uploaded
to a Postscript printer, will advise the printer to generate a printed
message upon an error condition.  This is very useful when the program
sending postscript files to the printer is so dumb it doesn't pay any
attention to the returned error codes.

If anyone out there knows what I'm talking about, please e-mail me the code.

Thank you.


	Lyle Wiedeman                 Office of Academic Computing
	wiedeman@uci.edu              Univ. Calif. Irvine
	wiedeman@UCI.BITNET           Irvine, CA  92717
    	(714) 856-8718	    	      FAX (714) 725-2069
--
	Lyle Wiedeman                 Office of Academic Computing
	wiedeman@uci.edu              Univ. Calif. Irvine
	wiedeman@UCI.BITNET           Irvine, CA  92717
    	(714) 856-8718	    	      FAX (714) 725-2069
Newsgroups: comp.lang.postscript
From: hank@ducvax.auburn.edu
Subject: Re: More on nenscript
Organization: Auburn University, AL
Date: Wed, 2 Sep 1992 23:18:18 GMT

In article <geoffw.715299917@extro.ucc.su.OZ.AU>, geoffw@extro.ucc.su.OZ.AU (Geoffrey Warren Hicks) writes:
> 
> Posted on behalf of Craig Southeren who does not have access to
> a net account:
> -------------------------------------------------------------------
> 
> Thanks to everyone who expressed interest in the nenscript program,
>    Keep the suggestions coming - I will really get to them as soon
> as possible.

My mailer bounced the following note. nenscript looks interesting, but please
don't forget the OS/2 users. There are some problems with the makefile 
(shouldn't __STDC__ be defined so that the prototypes get used? I get problems
if I don't use these.).  

With easy changes to the makefile, nenscript runs under OS/2. Context diff's 
follow.


Original message:

Thanks for nenscript. I've only briefly examined, as I do not have
all of ghostscript loaded. In any case, your makefile.msc needs some 
modifications for MSC 6.00A to produce OS/2 executables.  I have attached
the file produced by 'diff -c makefile.msc makefile.os2', in case it can
be of any help. 

Note:
1. your make line for the executable always fails, as the '.exe' is missing.

2. makefile.os2 will produce an OS/2 executable and a separate bound
executable (will run under OS/2 and MSDOS). 

--darrel hankerson hank@ducvax.auburn.edu



*** makefile.msc	Sun Aug 23 18:46:52 1992
--- makefile.os2	Tue Sep 01 19:42:34 1992
***************
*** 1,8 ****
! #
! # Makefile 
! #
! # $Id: Makefile,v 1.5 1992/05/26 23:15:19 craigs Exp $
! #
  
  OBJ		= .obj
  
--- 1,9 ----
! # Makefile for MSC 6.00A under OS/2. 
! # Adapted with minor changes from the supplied makefile.msc
! # Files:
! #  nenscript.exe	OS/2 executable
! #  nenscrib.exe   OS/2 and MSDOS bound executable
! # Darrel Hankerson hank@ducvax.auburn.edu, 1-Sep-92
  
  OBJ		= .obj
  
***************
*** 27,45 ****
  # US_DATE selects date of form MMM DD YY, else date is DD MMM YY
  #
  CFLAGS	=	-DUS_DATE $(DEBUG)
! LFLAGS	=	/F 5000
  
  CHMOD	=	chmod
  CP	=	cp
  RM	=	rm
  INSTALL	=	install
  
! all debug:	$(PROG)
  
! $(PROG): $(OBJECTS)
! 	$(CC) $(CFLAGS) -o $@ $(OBJECTS) $(LFLAGS)
  
  main.$(OBJ):	main.c
  
  clean:
  	rm -f $(PROG) *.$(OBJ)
--- 28,54 ----
  # US_DATE selects date of form MMM DD YY, else date is DD MMM YY
  #
  CFLAGS	=	-DUS_DATE $(DEBUG)
! LFLAGS	=	-Lp /F 5000
  
+ DEFS = -DMSDOS -D__STDC__
+ BIND = bind
+ 
  CHMOD	=	chmod
  CP	=	cp
  RM	=	rm
  INSTALL	=	install
  
! all debug:	$(PROG).exe nenscrib.exe
! 
! $(PROG).exe : $(OBJECTS) nenscript.def
! 	$(CC) $(CFLAGS) -o $@ $(OBJECTS) $(LFLAGS) nenscript.def
  
! nenscrib.exe : $(PROG).exe
! 	$(BIND) $< /o $@ 
  
  main.$(OBJ):	main.c
+ 
+ .c.obj :; $(CC) -c $(CFLAGS) $(DEFS) $<
  
  clean:
  	rm -f $(PROG) *.$(OBJ)
   

Newsgroups: comp.lang.postscript
From: lee@nuchat.sccsi.com (Bill Lee)
Subject: Re: EPSI?
Organization: /etc/organization
Distribution: comp
Date: Wed, 2 Sep 1992 02:16:01 GMT

In article <KFILES.92Aug31110335@virtual8.harvard.edu> kfiles@virtual8.harvard.edu (Kirby Files) writes:
>I have a variation on an FAQ.  How can one generate an EPSI format
>file?  I can transform a PS file to EPS no problem, that's trivial.
>But does anyone out there know where I can get my hands on a spec for
>EPSI, which apparently has some for of text encoded bitmap preview,
>and does anyone have any ideas for generating that preview. Perhaps
>using Ghostscript to generate a bitmap, and then somehow properly
>encoding that bitmap in correct EPSI format?

The spec for the EPSI format is in the Red Book. If you have the second edition,
it is on pages 730-732.

>
>I'm using FrameMaker on a Sun, and it's really particular about
>importing PS; it will only accept EPSI.  Any other ideas on getting
>FM to accept a PS file as graphic, and not text would be appreciated.
>
Actually, FrameMaker will accept EPS files without the preview image provided
in the EPSI format. The graphic will not be displayed since F.M. does not
interpret PostScript. The graphic area where the EPS file will be displayed
will be imaged as a light gray box (i.e., the bounding box of the EPS
image). The EPS file will be rendered properly when the F.M document is sent
to the printer (or other PS interpreter).

If you want F.M to actually display something when importing the EPS file,
you will have to get the preview image (which was the original question you
asked above).
>Thanks,
>------
>+   0__, ---     Kirby Files, 623-1673   | "Whoso would be a man     +
>      /   ------ 29 Banks Street         | must be a nonconformist"
>      |\   --    Somerville, MA  02144   | 
>+ ---**-**------ files1@husc.harvard.edu | Ralph Waldo Emerson       +


Regards,

Bill Lee
From: cdh@uk.ac.cam.eng (Chris Horne)
Newsgroups: comp.lang.postscript
Subject: Re: HPGL to postscript translator?
Date: 2 Sep 92 15:58:35 GMT
Reply-To: cdh@uk.ac.cam.eng
Organization: Cambridge University


Try searching on archie for hpgl2ps

I downloaded the source from src.doc.ic.ac.uk (146.169.2.1)
in /unix/wsmr-simtel20.army.mil/postscript/
files are hpgl2ps1.tar-z and hpgl2ps2.tar-z


The filter works fine, but not all the hpgl commands are implemented.

Chris

__
Chris Horne BEng ACGI | Tel: +44 223 332738 | University of Cambridge 
cdh@uk.ac.cam.eng     | Fax: +44 223 332662 | Department of Engineering
From: mark@gizzmo.UUCP (Mark Hilliard)
Newsgroups: comp.lang.postscript
Subject: Re: Fax2ps program desperately needed
Date: 29 Aug 92 00:31:42 GMT
Reply-To: mark@gizzmo.UUCP (Mark Hilliard)
Organization: gizzmo

In article <1992Aug27.222432.917@news.acns.nwu.edu> cmbecker@casbah.acns.nwu.edu (Canton Becker) writes:
>
>    I'm desperately need a fax2ps program that _works_.  (I've tried the

Contact Digiboard and ask for Rick Richardson.  Tell him your woes and
ask him if he will send or sell you his program.


Mark Hilliard


-- 
Mark Hilliard, Eastman Kodak  - mark@kodak.COM
                              - uunet!kodak!gizzmo!mark
Newsgroups: comp.lang.postscript