in reply to Array Exclusion Operationss

There's no way we can tell you what's wrong without seeing runnable code, sample input, sample output and desired output. See also How (Not) To Ask A Question.

One thing that strikes me is a bad is the usage of eval without sanity checks on the input (security risk), and not checking $@ afterwards to see if it went wrong.

Replies are listed 'Best First'.
Re^2: Array Exclusion Operationss
by harishnuti (Beadle) on Jul 09, 2008 at 13:53 UTC

    Sorry, i didnt put data because its huge, i was looking more into approach i.e. if i have done something wrong interms of array operations

    Thx for pointing out eval one, good one, noted it
      Sorry, i didnt put data because its huge
      --- [from wn] --- sample n 1: a small part of something intended as representative of the whole