Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!bgsuvax!edwards
From: edwards@bgsuvax.UUCP (Bruce Edwards)
Newsgroups: comp.lang.postscript
Subject: Re: input from files, postscript
Message-ID: <2115@bgsuvax.UUCP>
Date: 9 May 88 20:31:59 GMT
References: <1089@sask.UUCP> <2042@bgsuvax.UUCP> <9340@sol.ARPA>
Organization: Bowling Green State University B.G., Oh.
Lines: 40
Keywords: input, postscript

In article <9340@sol.ARPA>, ken@cs.rochester.edu (Ken Yap) writes:

[Ken Jenkins]
[ on shoving data into the code as arguments for operators I
write ,"yeah let's do it!" ] 

[Ken Yap]
> 
> I disagree. Do you propose I shove this bitmap screen dump of mine
> into the code instead of using readhexstring? Have a look at any recent
> raster to PS converter.  It would probably slow the thing down by
> tripling the code size. There are reasons why bitmap dumps are slow but
> inlining the data doesn't help.

I quite agree on your bitmap data. But I believe the original poster
was talking about data points to be used in the building of a graph
of some sort. For data of this type I still maintain embedding it as
arguments to operators is the quickest way to go.

> And yes, it makes sense for the data to go at the end of a PS file.
> Bit reminiscent of card jobs, no? :-)

Ah yes, the good ol' days.

> 	Ken


Disclaimer: I am participating as a guest of Bruce Edwards. My name
            is Ken Jenkins. Bruce is generally amused with my ramblings
            but does not necessarily agree with them.

            'These are only the shadowlands.' C.S. Lewis 
      ----------------------------------------------------------------- 
        Ken Jenkins as guest of edwards@bgsu
        
        CSNET: edwards@bgsu
      ARPANET: edwards%bgsu@csnet-relay
         UUCP: cbosgd!osu-cis!bgsuvax!edwards 

      -----------------------------------------------------------------