Cons is a tool for constructing software systems --- a Perl-based make replacement.
However, as I was reading through its docs, I noticed that it automatically would export scalars from a Cons program (nothing but a perl script that uses the Cons API) in one directory to a Cons program in another... poof! This means it does message passing for you without learning POE or Class::Tom or some other beast.
So now I unveil my tour de force, my arc de triomphe, my yo-check-it-out-daddy-its-megafresh, example of having Cons automatically serialize my data (ala, Data::Dumper or Freezethaw or Storable) and de-serialize it in another process:
# 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']);
$po = { 1 => 'two', 'buckle my' => 'shoo' };
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
RE: Object-Oriented Persistence and Message Passing with Cons
by mirod (Canon) on Oct 13, 2000 at 18:54 UTC | |
by princepawn (Parson) on Oct 13, 2000 at 19:07 UTC |