in reply to Re: Cor—An object system for the Perl core
in thread Cor—An object system for the Perl core

Alternatively, release and maintain a fork, maybe "CorPerl - Perl with objects"?

In that scenario, you'd be equivalent to RPerl and CPerl; you could get endorsement, support, maybe cash, from TPF. Because Perl is a family of languages, don't you know. Heck, maybe Will the Chill wants core objects, and y'all could get together and publish "CoRPerl", if fast is among your goals.


The way forward always starts with a minimal test.
  • Comment on Re^2: Cor—An object system for the Perl core

Replies are listed 'Best First'.
Re^3: Cor—An object system for the Perl core
by perlfan (Parson) on Jun 02, 2020 at 01:18 UTC
    I tried to upboat this more than once, but it won't let me.

    I've mention Qore here before. Although Perl folks pretend it doesn't exist and the creator of Qore at one point said he'd never heard of Perl. So idk, that's a little strange.

    Anyway, TFM says,

    Programmers familiar with C, C++, Java, and/or Perl should find the standard Qore syntax intuitive and should be productive fairly quickly with the language. However Qore has unique features that differentiate it from other languages, and these features must be mastered in order to leverage the full power of Qore.

    In fact, it goes well beyond, ...Perl (programmers) should find the standard Qore syntax intuitive and should be productive fairly quickly.

    Well I've found that it's demonstrably true that a useful subset of Qore is identical to a marginally useful subset of Perl.

    It's also:

    • truly SMP with real threading
    • supports $REAL OOP when you actually want it
    • super cool
    And I have mentioned this before, too. It's not my go-to language. Perl is. Why, despite knowing darn well what's good for me?
    • Qore is not perlish to the degree I want it to be
    • I don't need SMP, and when I think I do, fork works well enough for me (who needs child processes to communicate back with their parents? ha!)
    • I can assume perl is anywhere I need it to be

    Even if Perl and Qore pretend each other doesn't exist, it's still a better and less awkward love story than all the perl forks and broken dreams.

    Update - found this nice down about Qore on their GH wiki, Why Use Qore. And it's on MacPorts! (no they don't call it MacQore)...now I gotta go lookup MacPorts vs Homebrew.

    Update 2 - it occurred to me why I do prefer Perl. It's because it's the perfect tool for bending *nix to one's will. It turns a system into putty in a master's hands (or even a baby's). And that's why I use it. Of course implied is also it's fabulous community of free thinkers and hackers.

[reply]
[d/l]
[select]

      "I tried to upboat this more than once, but it won't let me."

      Unsurprising. Your links don't work, notes on how to do this properly are displayed each time you post.

[reply]
      I hadn't heard of Qore either, therefore more interesting for me would have been these linksYou wrote
      a useful subset of Qore is identical to a marginally useful subset of Perl.
      Depending on what exactly you mean by "identical" influences the size of the "subset". I see similarities, Wikipedia says "inspired", but not exactly identical...
[reply]

In Section Perl News