un/share deluge task too restrictive

I was really disappointed at how limited/restricted the deluge share task is.
What should have been a simple 1 line loop has turned into a 100 line routine due to the fact that this task requires a hard coded name that is validated for its existence at design time precluding the simple use of tables

rather than :
      for each rec in permissions[]
       {
             share (rec.item,user.email);
       }

we are instead forced to unwind it for each and every possible sharable item :
       if(item=="xxx_tab1")
       {
          share section("xxx_tab2",user.email);
       }
       if(item=="xxx_view")
       {
          share view("xxx_view1",user.email);
       }
       if(item=="xxx_form1")
       {
          share form("xxx_form1",user.email);
       }
       . . .

A few points :
for a database centric app dev system - this completely precludes the use of tables.
section/page/view names must be unique within an app - so why require the separate 'functions' - zoho knows what every item is it by its name.
since the name has to be known at design time - what is the purpose in requiring the name to be quoted ?