Dependent recipes?

I wrote a nifty equivalent of python's explode (*) operator that I thought I might post, but it depends on two other recipes that are useful on their own, remove_arg which removes the rightmost parameter from a function type, and bind_append which lets you bind a value to the leftmost unbound parameter of a function without specifying the number of parameters. Should I simply mention that the recipe depends on another? Should I include remove_arg and bind_append with the explode recipe? I posted it on comp.lang.c++ to no replies awhile back. explode itself is a bit messy and would need to be cleaned up but remove_arg and bind_append should be fine:

http://tinyurl.com/2blrs8

Joseph Garvin said

I wrote a nifty equivalent of python's explode (*) operator that I thought I might post, but it depends on two other recipes that are useful on their own, remove_arg which removes the rightmost parameter from a function type, and bind_append which lets you bind a value to the leftmost unbound parameter of a function without specifying the number of parameters. Should I simply mention that the recipe depends on another? Should I include remove_arg and bind_append with the explode recipe? I posted it on comp.lang.c++ to no replies awhile back. explode itself is a bit messy and would need to be cleaned up but remove_arg and bind_append should be fine:

http://tinyurl.com/2blrs8

It might be nifty to put them in as separate recipes. You can link the first recipes from your explode operator using internal links. If you look at the properties of this recipe you'll see an internal link to Boost.Bind, but don't worry too much about doing it. We can always tidy up the text and add the links once the recipes are in.

I'll have a think about adding a uses recipes facility to the site as well…