Re: Re: Re: Post Processor

Seems to me that there is a bit of a stretch here concerning the
differences between a "real" post processor and a "config" file driven
cam. I'm curious to know what a post can do that a config can't? Uh,
other than cost you a bunch of cash!

Beyond that -- and it may well be my ignorance of the nuances here -- it
seems to me that a lot of us could write a post-post processor using any
common language or macro intensive package that would read the output of
about any reasonable CAM post or config and submit it to a few rules that
would modify it to a specific device or variant of rs274.

Ray

BTW for those who feel compelled to keep track of these things, I've sold
a couple of Vectors for Imserv long years ago.

>    From: Doug Harrison <prototype@...>
> Subject: Re: Re: Post Processor

<s>

> Writing one is out of the question as the syntax is spaghetti, probably
> intentionally so. You would be dollars ahead to buy Dolphin or Vector
> before spending money on a Mastercam post.  The post will cost more
> than either of these packages.  I bought Bobcad (didn't know about the
> other two) and still use it for all 2D work because it's less trouble
> than Mastercam.