in reply to A port of "Dukedom" to Perl

To clarify, are you more interested in setting up a particular display system that's portable or, say, creating a layer of some sort so that different display systems could be accommodated? I'm assuming the latter...

Replies are listed 'Best First'.
Re^2: A port of "Dukedom" to Perl
by Tux (Canon) on Oct 08, 2014 at 05:55 UTC

    For portability and speed, I would advice to use Sereal instead of Storable.


    Enjoy, Have FUN! H.Merijn
[reply]

      Thanks for the tips, Tux and YM!

      I'm thinking about Storable because it is in CORE. JSON is also high in my opinion (and probably should be part of CORE given how pervasive it is.) I'll have to check the others.

      You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
[reply]
        $ corelist JSON::PP

Data for 2014-10-01
JSON::PP was first released with perl v5.13.9

        [download]

        Storable is in CORE, but it has portability issues: it is not guaranteed accross architectures or versions. JSON and Sereal are.


        Enjoy, Have FUN! H.Merijn
[reply]
[d/l]
Re^2: A port of "Dukedom" to Perl
by boftx (Deacon) on Oct 07, 2014 at 22:11 UTC

    Yes, the latter. I seem to be coming up with a state-machine approach that saves state whenever input is needed (via Storable and SQLite?) and then throws an exception object (Throwable) that alerts the application code to what kind of input is needed and how to re-enter the state-machine once it is available.

    Conceivably there could be helper modules implementing a Display Role.

    You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.
[reply]

      And there are others besides what Tux brought up; Data::MessagePack for (maybe best?) speed and JSON::XS for Storable-level speed + human readability + best portability.

[reply]

In Section Meditations