Re^4: perlcc not working

[rurban]

Your citations are wrong.

perlcc did not die, it was rather enhanced, improved, it is used in production for over 10 years and is under continuous development.

perlcc was just removed from core (p5p was not able to maintain it anymore).

pp is no compiler, it is a packager.

[marto]

Thanks. It was not my intention to suggest that pp is a compiler, without doing some searches I'm fairly sure that I frequently use the term packge or packager when discussing pp.

Apologies if I've misrepresented perlcc, I was purely basing this on the documentation I read, which I quoted in this thread, and the experience of other users, rather than first hand experience of perlcc. In this thread the user was having problems, I suggested an alternative course of action to achieve if similar (but different) end result.

[Anonymous Monk]

The docs themselves still say

The code generated in this way is not guaranteed to work. The whole codegen suite (perlcc included) should be considered very experimental. Use for production purposes is strongly discouraged.

[Anonymous Monk]

Yup, packagers like PAR/pp/citrusPerl only package executables, but that is what most like puneet are after -- an installable myprog.exe that works out of the box

perlcc might compile on puneet's machine, but generally it just doesn't compile on most machines.

It never compiled on win32, while PAR/pp/citrusperl will gladly churn out an .exe