Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #2973

Re: Dev Environment for Postscript - solutions/desiderata?

Show all headers | View raw

On 2016-12-14, luser droog <luser.droog@gmail.com> wrote:

> My experience with C programming is that it is often better
> to organize programs into multiple source files so related
> functions are together and the program pieces obey a 
> "module discipline" to interoperate, the sum of which 
> supports the needed functionality of the program.

Right.

> I feel in my bones that my postscript code should be
> better organized in this direction. Even a highly
> "modular" program like ibis presents a barrier to
> understanding by the simple fact that it's all stuffed
> into one file. Eg.
>
> http://codereview.stackexchange.com/questions/117320/document-formatting-markup-engine-in-postscript
>
> The code is "just a big wall of text" at first glance,
> and 90% of potential answerers don't have the energy to
> penetrate to the good stuff (hypothesis).
>
> But PostScript doesn't quite have the tools that a C
> programmer has with make and the pre-processor.
>
> We have 
> http://www.math.ubc.ca/~cass/graphics/manual/code/psinc
> but it needs modification to cope with indented (file)run
> commands.
>
> Has anyone else come up with solutions for working with
> multi-file postscript "applications" and automatically
> producing amalgamated sources which are compatible with
> -dSAFER?

Some years ago, I wrote a program that does what you're
describing : replace "(file) run" operations with the contents
of that file. It's a quick hack but it does what I need.

> What other "nice to have"s are there for building bigger
> things with PostScript?

There's another program like cat -n except that the number is
the file offset of the first character of the line. Helps locate
errors in your PostScript code (Ghostview/Ghostscript likes to
tell you at which /file offset/ errors occurred).

DSC requires far more boiler-plate than I can remember, let
alone type. I've been meaning to write a preprocessor to take
care of that for me.

-- 
André Majorel http://www.teaser.fr/~amajorel/
"Pauvreté n'est pas vice ! Parbleu ! Un vice est agréable."
  -- _Passe-temps_

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Dev Environment for Postscript - solutions/desiderata? luser droog <luser.droog@gmail.com> - 2016-12-13 21:42 -0800
  Re: Dev Environment for Postscript - solutions/desiderata? luser droog <luser.droog@gmail.com> - 2016-12-13 23:39 -0800
  Re: Dev Environment for Postscript - solutions/desiderata? jdaw1 <jdawiseman@gmail.com> - 2016-12-14 01:20 -0800
  Re: Dev Environment for Postscript - solutions/desiderata? Carlos <angus@quovadis.com.ar> - 2016-12-14 16:49 +0100
  Re: Dev Environment for Postscript - solutions/desiderata? Andre Majorel <cheney@halliburton.com> - 2016-12-15 22:20 +0000
    Re: Dev Environment for Postscript - solutions/desiderata? luser droog <luser.droog@gmail.com> - 2016-12-17 00:58 -0800

csiph-web