wxport

[Kai-Uwe Behrmann]

Am 16.05.03, 15:59 +0300 schrieb Juha Helminen:

> Hello,
>
>  > > > BCB do not manage to compile

#ifndef __BORLANDC__
>  > > > extern "C" {
#endif
>  > > > #include <pano12/filter.h>
#ifndef __BORLANDC__
>  > > > }
#endif
.. as a suggestioni <- works for gcc.

Paolo, how can such macro variables like __BORLANDC__ or __cplusplus be
viewed? Is there an compiler option for showing?

> PanoTools source is not easy to follow. Is it easier to rewrite
> functionality to C++ than than to make some C++ components that hides
> C-structures. PT is build with global variables (atleast one "global"
> pointer) and all routines are not so nicely converted to C++, or how?
>
> Too much work to rewrite PT, I think, better to make GUI that uses old
> style/library.

Ok so I would agree with and like to replace all text chars with "string".
Can You with bcb compile following?:

 using namespace std;
 #include <string>

 string a ("Hallo");
 string b = a;

?
Exchanging could help me detecting the bug wich causes ptopengui to crash
after parsing an script - hope so.

>  > But some time in the future I might need some functionality from
>  > libpano, like partial undistortion of images.
>
> This is good reason to use it directly. I have tried to read how to do
> this but it's not so easy to find out. Final panorama has y=0,p=0,r=0. I
> suppose that y, p and r can be made as variables ;)
>
> Juha
>

... and I will throw away my code of the last week.
Kai-Uwe