Re: Export more API functions to Perl clients
> + @_all_fns = qw(add add3 blame blame3 cat cat2 checkout checkout2 cleanup
> + commit commit3 commit_item2_dup copy copy3 delete delete2
> + diff diff3 diff_peg3 diff_summarize diff_summarize_peg
> + export export3 import import2 info info_dup list lock
> + log log2 log3 ls ls3
> + merge merge2 merge_peg2 mkdir mkdir2 move move4
> + propget propget2 proplist proplist2 proplist_item_dup
> + propset propset2 relocate resolved revert
> + revprop_get revprop_list revprop_set
> + status status2 switch unlock update update2
> + url_from_path uuid_from_path uuid_from_url);
Isn't there any way to hide the interface revs behind the bindings?
Like most scripting languages, Perl can be much more polymorphic than
C. It's not like the API matches up exactly anyway, unless you expect
Perl apps to manage pools manually.
Maybe it is wishful thinking on my part.
Received on Tue Mar 21 21:02:00 2006
This is an archived mail posted to the Subversion Dev