On 12 Oct 2003 14:17:30 +0200, Tomas wrote:
>
> Hello. I was missing some functionality (specifically saving the position
> and size of windows) so I started to develop a module. The problem is that
> I don't like C very much, so I tried to do it in c++, after hacking some
> scripts and headers, which caused some compilation and linking errors.
>
> So, my question is: is it worth the effort to try to make some sort of
> c++-interface to the modules? I was thinking of doing it in that case, but
> I ask of your opinions first since I'm not really into the code yet.
> Because I believe that my problems could be solved this way, and also, it
> could be a nice project :)
You should know the internals pretty well to consider to do such project.
You should also learn perllib thorouhly, because you will want to reuse
its class design (if you dislike C function approach). At this point, you
probably decide just to stick with Perl, because you will not be able to
find C++ equivalents for many elegant Perl solutions. In this regard, C++
is not much different from C.
> Additionally, in the configure-scripts I read that: "Actually, we don't
> use it (c++) at _all_ anymore, since the only module that used it has been
> removed. It causes problems so we'll comment it out for now. Hopefully
> by the time we need it again autoconf will handle it better :-/ "
> What are these problems? Is my project doomed, or could it be solved?
Dan already answered, but I may add some bits.
You may see how FvwmKb (use Google) solved this. I think it has its own
Makefile.
If you describe exactly what do you need to do in your module, it is
possible there is a solution without additional modules.
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Oct 12 2003 - 08:42:18 BST