[Gs-devel] Re: Dynamic driver loading

LOUIS-SIDNEY Rodolphe sidney at gcu-geot.insa-lyon.fr
Thu Feb 1 04:22:21 PST 2001


Raph wrote :
Subject: Dynamic driver loading

>    A few more details: Sidney's dlopen code covers more targets than
> Iain's, which is good. On the other hand, it relies too heavily on
> #ifdefs. I'd rather see the code divided into gp_*.c, with #ifdefs for
> the various flavors within a file (ie, elf and a.out within
> gp_unix.c). I believe the gmodule component of glib will be an
> excellent source of information on making dynamic loading work on a
> wide variety of target platforms.
>
I don't have all the built platforms of Ghostcript ...
I try to put the code in a one file. But we can do differently. Put a code
for a specific platform (gp_*.c) , it will be different, dependent the
facilities of the platform.
We have one point of beginning ... Perhaps it will better to use libtools ?


>    The formatting and indentation of Sidney's code is not consistent
> with Ghostscript standards (nor with itself). Among other things, this
> gives a bad impression. To get accepted, a patch will have to have
> neat, clean formatting.
>

This code to be improved, it's an alpha code to show it will be possible to
do it :)
I 'am conscious it is not a perfect code and it have somme lack functions
like versionning,
emumerations of driver. I modify the postscript code and not implement the
install the code to be functionnal ...
( Are you a little maniac or too perfectionist ?)
I a not a real computer scientist, not known about all the rules for
programming, and organising code. There is more big difficulties to resolve
I think.
The best for us is to a precise idea of what we want to do and how to do it.
I don't have enough knowledge of the internal mecanisms of ghostscript and
how to do for the best. I'am convinced we need the best of ian's code and
mine to reach our goals. I don't have THE SOLUTION.


To be continued.





More information about the gs-devel mailing list