Power render and C++

Azrael · 2000-06-19T16:46:35

This is an important topic about PR, So I think i could start a thread about it, heres a few pointers about using PR and C++ 1.-Power render is pure C This is probably the most important point, using C++ OOP and PR must be considered as PORTING it will work but it wont be "automatic switching". 2.-Use globals, some variables in PR need to be accessed by almost all functions, the best way to do this is to use globals, this totally brakes OOP laws, but it works so what the heck? Some globals recomended to be used... viewport, cameras, terrain, etc. if a variable is giving you problems to access it, use it as a global. Eventually you could make them work into a class somehow, but my advice is to simply avoid the headache and make it work as a global. 3.-Some things wont work as C++ There are some PR functions, variables,methods that wont work from inside a class, like callback functions and such, learn what this are, and take them out of the class and to another c file then call it as an extern c. 3.-Use Extern C, this will solve a lot of problems... you can use an actual function from c in c++ with total c syntax by using this carefully. 4.-Remember to change .c to .cpp this solves problems, and yes in the heat of a project and a deadline you can forget that classes wont work in .c files 5.-changing the winutil.c is possible, of course it is, as a matter of fact winutil didnt existed back in PR 2.5 and it still worked, thats like saying you cant make landscapes without landscape studio. It just gets a bit more dificult... and you will probably have to touch win32 and dx coding, newbies should avoid this. extra tip for visual c++ users: are you tired of seing the pr dialog?, just take it off your project and compile it, pr will switch to defaults automatically, you will have to put settings by hand if you are not using defaults but is nice to know. I usually do this for quick testing, and add a dialog for release(a modified dialog that is) 6.-Check the oop example very, very carefully to see more pointers. 7.- add your pointers and opinions, to this thread

Power Render API Affiliates

Started by Azrael June 15, 2000 03:39 PM

16 comments, last by Azrael 23 years, 10 months ago

Azrael

128

Author

June 16, 2000 02:51 PM

Thanks whirlwind there were the proper minus signs on that line but this forum didnt showed them

I will send you the errors I get maybe we can fix this together

And voodoo if you change the extensions from .c to .cpp the compiler automatically reads it as C and C++ code, (almost all c++ compilers do, Im assuming you use visual c)if you dont believe me try it, you will notice the compiler gives you warning or errors you didnt before.. (if you are using classes or c++ code of course

)

On a curious note: In unix and GNU you can even use c and C to or c and cc and the compiler takes it as c and C++ code respectively..

Azrael

128

Author

June 17, 2000 11:24 AM

Has anyone tried to convert land1 to cpp?
Im getting some weird error in the winutil.cpp file...
should I leave that file as it is?

btw the (void *) errors can be fixed by using a cast...
no problem there...

Azrael

128

Author

June 17, 2000 11:57 AM

I have an idea, maybe this wont fly but is worth to try...
why dont we start a community effort
and post CPP versions of the Pr examples?
maybe chris can upload them to the egerter web page...
this may seem silly but I think we may all get benefit from...

diferent winutil files...
c++ classes wrapping pr.. etc.
I think this is a good idea

Whirlwind

134

June 18, 2000 04:09 PM

I leave town for 3 days (no computer access by the way), and I end up helping Azreal somehow... is that good?? If I go on vacation for a week, will that fix all the compile time errors he is having?

Gary

122

June 19, 2000 02:24 PM

Two weeks should do it...

Gary

Whirlwind

134

June 19, 2000 02:53 PM

At this point I should be calling my mommy for some re-affirmation.....

Azrael

128

Author

June 19, 2000 03:30 PM

Well... since I did this thread I should also continue it..
so heres another pointer...

Wrapper classes: This is probably the best (and in some cases the only way) to convert some examples or PR based engines into actual working c++.

How does this work? use higher level functions that execute PR code inside them but leave this original code as it is.. just call it... in our dear Land1 that means calling LoadTerrain from load.c or a function inside load.c made in c per example setfogrange...
Also you can subdivide the function in c and call it from a more complex wrapper function.
Per example:
Terrain::LoadTerrain
{
setfogrange; //This function is set on load.c
loadterrainsections //this function is also set on load.c
LoadCharacters //This can be a function from your own code
}
(this is what im using now to compile in c++ land1

)

Correct me if im wrong.. I will be a real fool, if im not able to accept and learn from my own mistakes.

Whirlwind

134

June 19, 2000 04:46 PM

ChrisE was nice enough to group things in the lstudio.h file for lstudio. It shouldn''t be too hard (yeah, ok like anything is..

) to port 75% of it to C++. So you are just making land1 functions accessible as a single call from C++, and globals are kept globals?

Power render and C++

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Power render and C++

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines