Re: RFC: Case package documentation

I'm trying to figure out ... this isn't re-entrant, is it. Which means, no embedding Case's inside other Cases - even indirectly? Be forewarned: this can make your module extremely limited.

Of course, Perl does offer some help here - the sub ref you return can localise your stack, and that should help, although it may not be perfect.

Comment on Re: RFC: Case package documentation

Replies are listed 'Best First'.
Re^2: RFC: Case package documentation by Roy Johnson (Monsignor) on Jun 03, 2005 at 12:32 UTC
I haven't tested embedding cases, but I don't see any reason you couldn't. I think there must be something unclear about my documentation to have given you that impression. What made you think that? You can download the package from where I've stashed it if you want to play with it. There's no installation stuff (Makefile.PL), you just unpack it and work within the Case directory. There is a small test suite (t.pl, runs tests in the t subdirectory) that should illustrate how I designed it to be used. (Of course, my goal is to have the docs explain it without the need for more clarification.) The interface is definitely different from Switch, which is the reason I named the function dispatcher: the function gives you a dispatcher, rather than acting like a piece of flow-control syntax. Ok, I just added a simple test for embedded cases, and it works. It's not in the stashed version. To the end of smatch.t, I've added `# $smatch was created by a previous call to dispatcher my $embed = dispatcher( ['ok'] => sub { $smatch->($_) } ); is($embed->('ok'), 'resumed and matched', 'embedded smatch');` [download] Caution: Contents may have been coded under pressure.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: RFC: Case package documentation
by Roy Johnson (Monsignor) on Jun 03, 2005 at 12:32 UTC

You can download the package from where I've stashed it if you want to play with it. There's no installation stuff (Makefile.PL), you just unpack it and work within the Case directory. There is a small test suite (t.pl, runs tests in the t subdirectory) that should illustrate how I designed it to be used. (Of course, my goal is to have the docs explain it without the need for more clarification.)

The interface is definitely different from Switch, which is the reason I named the function dispatcher: the function gives you a dispatcher, rather than acting like a piece of flow-control syntax.

* Ok, I just added a simple test for embedded cases, and it works. It's not in the stashed version. To the end of smatch.t, I've added

# $smatch was created by a previous call to dispatcher
my $embed = dispatcher( ['ok'] => sub { $smatch->($_) } );
is($embed->('ok'),
   'resumed and matched',
   'embedded smatch');
[download]

Caution: Contents may have been coded under pressure.

[reply]
[d/l]