Per Hedbor () @ Pike (-) developers forum wrote:
>How about having a specific function for that instead of (string)?

>From a performance standpoint, that shouldn't be a problem.
Any suggestions as to the name of the function?

I'd say something like:

        gather(({"abc",({65,65,66}),"def",65})) => "abcAABdefB"

>The original magic '*' operator can be implemented using

>array magic = ({"abc",({65,65,66}),"def"});

>((array(string))magic)*"x" 

Yes, but that kills performance, since it creates a (at least one) temporary
string (per subarray) in the process.

>without special code in '*', btw.

If gather() (as above) is allowed in, then I can take out the changes to "*"
(except perhaps the tighter error checks which seem prudent).
-- 
Sincerely,
           Stephen R. van den Berg.
"I don't have to take this abuse from you --
 I've got hundreds of people waiting to abuse me."
  • Support for array(str... Stephen R. van den Berg
    • Support for arra... Martin Stjernholm, Roxen IS @ Pike developers forum
      • Support for ... Peter Bortas @ Pike developers forum
        • Re: Supp... Stephen R. van den Berg
          • Re: ... Per Hedbor () @ Pike (-) developers forum
            • ... Stephen R. van den Berg
              • ... Marc Dirix
                • ... Stephen R. van den Berg
              • ... Mirar @ Pike developers forum
                • ... Marc Dirix
                • ... Mirar @ Pike developers forum
                • ... Stephen R. van den Berg
                • ... Peter Bortas @ Pike developers forum
                • ... Stephen R. van den Berg
                • ... Peter Bortas
          • Re: ... Martin Stjernholm, Roxen IS @ Pike developers forum

Reply via email to