Re: Message Passing and Object-oriented Persistence... via Cons!

[Greg Spencer]

Maybe I'm missing something, but what's the difference between what you're
talking about (in terms of communication between processes) and just calling
'fork' to duplicate the environment and execute the DataDumper (or whatever
you would otherwise execute)?

IOW, I only see one-time, one-way communication here.

And, no, that's not the intended use of Cons :-)

            -Greg.

----- Original Message -----
From: <address@hidden>
To: <address@hidden>
Sent: Friday, October 13, 2000 8:38 AM
Subject: Message Passing and Object-oriented Persistence... via Cons!


>
> This is probably not the intended use of Cons, but since it automatically
> exports Perl scalars to-and-from build scripts, this can serve as a means
of
> shutting Perl data between Perl processes...
> ie, persistence and serialization without effort.
>
> Here is my simple example:
>
> # This is a Cons "Construct" file. It exports a scalar
> # named po, which is received by the perl program
> # tmp/Conscript
> $po = { 1, 'two', 'buckle my', 'shoo' };
> Export qw (po);
> Build  qw (tmp/Conscript);
>
>
> # This is the tmp/Conscript. I receive serialized data and
> # process it, in this case, simply printing it to STDERR
> Import qw( po ) ;
> use Data::Dumper;
> warn Data::Dumper->Dump([$po],['po']);
>
>
> Output of run is
> $po = {
>         1 => 'two',
>         'buckle my' => 'shoo'
>       };
>
>
>
> _______________________________________________
> address@hidden
> http://mail.gnu.org/mailman/listinfo/cons-discuss
> Cons URL: http://www.dsmit.com/cons/