in my last post I forgot to mention the following with respect to R and
"R can be built as a shared library1 if configured with ‘--enable-R-shlib’.
library can be used to run R from alternative front-end programs."
2011/4/16 Jon Kleiser <jon.klei...@usit.uio.no>
> Hi Thorsten,
> 1. No, none of the OpenGL libraries included with PicoLisp is complete.
> If there are functions or constants that you're missing, just let us
> know. Maybe you figure out how to add them yourself. It's not very hard.
> Are you using the 32- or 64-bit PicoLisp? The OpenGL libraries for these
> two PicoLisps are implemented quite differently.
> 2. Those hex values are just plain integers. In this case we could just
> have written (def 'GLUT_RGB 0).
> On Sat, 16 Apr 2011 14:27:15 +0100, Thorsten
> <gruenderteam.ber...@googlemail.com> wrote:
> > Hello List,
> > besides being on the road I keep studying PicoLisp a bit, and I´m
> > trying to understand the openGL library.
> > It seems almost too easy to be true, but I still have a few
> > questions:
> > 1. Is that a complete integration of OpenGL into PicoLisp, or just a
> > partial integration of the most usefull functions and constants? I
> > don´t know nothing about OpenGL, but it seems to be huge, and for
> > example looking up the GLUT library I found 19 callback functions,
> > while there are only 8 in the openGL lib.
> > 2. I don´t understand the constant definitions, for example:
> > (def 'GLUT_RGB (hex "0000"))
> > What is that hex value standing for, and how is it choosen for the
> > respective OpenGL constant?
> > When back home, I would like to write similar PicoLisp libraries for
> > GRASS GIS and maybe R (although its huge) - it doesn´t seem too
> > dificult, and would be very useful.
> > Cheers
> > Thorsten
> UNSUBSCRIBE: mailto:email@example.com?subject=Unsubscribe