Leon Timmermans

I don't think I can support building it that way currently. Building libperl++ requires a rather specific setup, and including all of that in a MSVC project may not be...

Windows has a nasty habit of defining various types like these. VOID is one of them (for a more complete list, see http://msdn.microsoft.com/en-us/library/aa383751%28VS.85%29.aspx). Making it compile on windows requires some...

Hi Shmuel, Thanks for all the feedback, it's really helpful. - evalutate.c: The include is missing deliberately. It doesn't need it and it would only slow down compilation. - glob.C:...

Erm, evaluate.C doesn't use IV/NV types, it just declares a string that will be evaluated by the interpreter. Yes, by all means include libperl++ in your talk. I'd be happy...

I now understand what you meant with the evaluate.C problem. IV/NV and friends should be defined in config.h, but that is empty on Windows for some reason. I'm going to...

I hadn't realized the ppport issue, that was certainly not the intention. IMO the LGPL is unfortunate in this particular case, but that wasn't my choice. I'm considering replacing the...

OpenSSL may not be around on all systems, its license is a bit tricky in its own way, and Crypt-OpenSSL-AES doesn't implement the cryptographic modes (Crypt::CBC and the like add...

I have the impression they're actually different things. I think the `incpth` description is correct but the `incpath` one isn't. I'm not sure I fully understand `incpath` but it seems...

> Here, $XYZZY is some temporary directory used on the build system that is not present on end user systems where the product is installed. You really should use `DESTDIR`...

> Installation seems to go fine, although it created the directory $XYZZY/perl_538... (yes, dots were appended there). I don't think the `-Dprefix=.../` should be used. That's really only for `@INC`...