Post Reply 
IFTE odd behaviour
10-11-2019, 09:09 PM
Post: #9
RE: IFTE odd behaviour
(10-11-2019 08:52 PM)David Hayden Wrote:  
Code:
result = {}
for each item in list
    temp = DoSomething(item, arguments)
    result = concat(result, temp);
That's easy to remember, defensible, and probably easy to implement.
It means that any list processing with an empty list gives an empty list as a result.

I agree.

More importantly, the returned result is *always* a list.
This helped the programmer to simplify code without hitting a "0" exception.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
IFTE odd behaviour - BruceH - 10-11-2019, 10:55 AM
RE: IFTE odd behaviour - Tim Wessman - 10-11-2019, 11:09 AM
RE: IFTE odd behaviour - rprosperi - 10-11-2019, 05:36 PM
RE: IFTE odd behaviour - rprosperi - 10-12-2019, 01:40 PM
RE: IFTE odd behaviour - Carsen - 10-12-2019, 06:41 PM
RE: IFTE odd behaviour - rprosperi - 10-12-2019, 10:49 PM
RE: IFTE odd behaviour - BruceH - 10-11-2019, 06:18 PM
RE: IFTE odd behaviour - Tim Wessman - 10-11-2019, 12:32 PM
RE: IFTE odd behaviour - ijabbott - 10-11-2019, 04:36 PM
RE: IFTE odd behaviour - Claudio L. - 10-11-2019, 08:36 PM
RE: IFTE odd behaviour - David Hayden - 10-11-2019, 08:52 PM
RE: IFTE odd behaviour - Albert Chan - 10-11-2019 09:09 PM
RE: IFTE odd behaviour - Wes Loewer - 10-12-2019, 06:38 AM
RE: IFTE odd behaviour - John Keith - 10-12-2019, 11:41 AM
RE: IFTE odd behaviour - StephenG1CMZ - 10-12-2019, 08:26 AM
RE: IFTE odd behaviour - Wes Loewer - 10-12-2019, 11:00 AM
RE: IFTE odd behaviour - Wes Loewer - 10-12-2019, 11:46 AM
RE: IFTE odd behaviour - John Keith - 10-12-2019, 11:50 AM
RE: IFTE odd behaviour - rprosperi - 10-16-2019, 04:25 PM
RE: IFTE odd behaviour - rprosperi - 10-17-2019, 03:29 PM



User(s) browsing this thread: 1 Guest(s)