Tomas <[EMAIL PROTECTED]> writes: > 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 :) > > 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?
As I remember, C++ worked, it was that the module wasn't worth the extra portability issues. I'd guess Perl would be the best language for a module like this. -- Dan Espen E-mail: [EMAIL PROTECTED] -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
