PB3.50 Win32 - Orge 3D Engine DLL

[BackupUser]

Restored from previous forum. Originally posted by tinman.

Originally posted by CodeMeister

used currently by the Blitz3D community, userlibs. The ability to extend the language to other capabilites such as OGL without

You've obviously not noticed that "PureLibraries" drawer, which is where the vast majority of the commands live. There is not many things which are internal to the compiler.


--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)

[BackupUser]

Restored from previous forum. Originally posted by CodeMeister.

Hmm, maybe I'm missing something here but it seems that, at least to me, there is a difference between this:

PureBasic is a complete programming langage which use third parts
libraries (called 'PureLibraries' to avoid conflit with systems
libraries) to ease the programmer life. These libraries can be wrote
in ASM (with NAsm or FAsm) or in C (with LccWin32).

and This:

.lib "Glu32.dll"

gluErrorString%(errCode%):"gluErrorString"
gluGetString%(nname%):"gluGetString"
blitz_gluOrtho2D(nleft_l%,nleft_r%, nright_l%,nright_r%,nbottom_l%,nbottom_r%,ntop_l%,ntop_r%):"gluOrtho2D"
blitz_gluPerspective(fovy_l%,fovy_r%,aspect_l%,aspect_r%,zNear_l%,zNear_r%,zFar_l%,zFar_r%):"gluPerspective"
blitz_gluPickMatrix(x_l%,x_r%,y_l%,y_r%,nwidth_l%,nwidth_r%,nheight_l%,nheight_r%, Viewport*):"gluPickMatrix"
blitz_gluLookAt(eyex_l%,eyex_r%, eyey_l%,eyey_r%, eyez_l%, eyez_r%, centerx_l%, centerx_r%, centery_l%, centery_r%, centerz_l%, centerz_r%, upx_l%, upx_r%, upy_l%, upy_r%, upz_l%, upz_r%):"gluLookAt"


Perhaps the ends justifies the means. The point I intended was this; in the .cdecls file in Blitz it's possible to code the function declarations directly in the Blitz language without resorting to coding the .dll portion. It was not necessry to understand the .dll coding structure itself, only the API parameters.
Of course, a .dll must exist in the first place so I guess it doens't matter who codes it... in this case the Glu32.dll was already available.
Six of one, half a dozen of the other... 8^)


"In God we trust, all others we virus scan." ~Author Unknown

[BackupUser]

Restored from previous forum. Originally posted by tinman.

Originally posted by CodeMeister

Perhaps the ends justifies the means. The point I intended was this; in the .cdecls file in Blitz it's possible to code the function declarations directly in the Blitz language without resorting to coding the .dll portion. It was not necessry to understand the .dll coding structure itself, only the API parameters.

You can also convert a DLL for use with PB, if that is what you are asking. Does the GL stuff use doubles? If so, that is one reason why a PB library was created rather than simply using the GL stuff directly (since PB does not currently have doubles).


--
I used to be a nihilist but I don't believe in that any more.
(Win98first ed. + all updates, PB3.51, external editor)

[BackupUser]

Restored from previous forum. Originally posted by CodeMeister.

The OGL API does make use of doubles. However, it was fairly straightforward to
code a single/double conversion routine using a "bank" in B3D code. The conversion routine is included as a auxilliary file. I've wondered why neither PB or B3D/B+ core code includes doubles? Architecture dependent feature I guess. Hmm...
Again, I'm not being critical of PB over B3d/B+ or vice versa. I'm currently using PB to code a GUI for a client based on it's, IMO, superior feature set over Blitz+...

"In God we trust, all others we virus scan." ~Author Unknown