Option to translate old-style perl code into emoji
Opened this issue ยท 3 comments
Hi there,
I really appreciate your work here. It's really important that the perl community (which is not famed for being up-to-date) steps into the modern programming era and adopts new programming paradigms, such as using shitloads of memory, and having emoji absolutely everywhere.
I have many programs on my computer written in regular, old-style perl 5 which I would like to translate and get rid of immediately! It would be great if emoji-perl
included an option to do this translation work automatically.
Another really cool feature would be to immediately crash at compile time unless the system hostname includes an emoji -- such antiquated systems should not be running our modern modern perl code!
Cheers,
Alex
Hello Alex,
Thank you for your interest in the EmojiPerl project, a translation engine is a really good idea and I will start working on that asap !
Regarding the other features you are describing, that sounds even better, Feel free to write a pull request if you desire to start the implementation of this perfect idea
Regards,
Jules
Hi Jules,
Thanks for the positive feedback!
I think it would be good to have a transition period in which checking the hostname at compile time is completely optional. It is important to maintain compatibility with some older machines for the time being, to ensure that new technologies can be properly adopted.
My proposal is to introduce a command line switch to enable hostname checking. This would require the inclusion of GetOpt::Std, a module included in the core perl distribution.
Would this be okay by you?
Regards,
Alex.
Update: I have just checked, and GetOpt::Std is not included in Perl on OpenBSD. It would be possible to implement simple option switches without using GetOpt::Std, which would increase compatibility without introducing dependencies.
That's sound really good !
A clear, emoji filled, warning should also be returned to the user trying to compile without an emoji in the hostname.
It might also worth looking at the interaction with CI tools like Jenkins, to see if tests can be run with an emoji hostname without problems.