Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.postscript > #2565
| Newsgroups | comp.lang.postscript |
|---|---|
| Date | 2016-05-11 22:47 -0700 |
| Message-ID | <27cddb20-29ce-40f7-bfa2-1df034bef8b5@googlegroups.com> (permalink) |
| Subject | how do filters work (internally)? |
| From | luser- -droog <mijoryx@yahoo.com> |
I've been digging into some pdf tutorials and (old) specs
(cuz they're shorter) and one major facility that I think
xpost will need in order to handle pdf (whether input or
output) is filters.
So, as usual, I'll just ramble and speculate out loud.
Please jump in if I make a stupid.
Filters seem to require a further degree of polymorphism
from the file operators. Eg. read will need to interface
between two implementations, something like
errcode ps_read (object f){
if (is_filter(f))
return filter_read(f);
else
return file_read(f);
}
and similarly for write. If other operators like
readstring and readhexstring are implemented in terms
of read, then no changes to them should be necessary.
And the various available filters are also collected
into a Named Resource, right? So I'll need to beef-up
my implementation of that, too.
Hm. That's all I've got so far.
Back to comp.lang.postscript | Previous | Next | Find similar | Unroll thread
how do filters work (internally)? luser- -droog <mijoryx@yahoo.com> - 2016-05-11 22:47 -0700
csiph-web