Functional PHP Extension

[eluser]sophistry[/eluser]
@Jamongkad - thanks for the new sample code. however, i am having a hard time understanding the benefits of adopting this coding paradigm.

the revised example you offer above shows the lambda function defining a new function that is essentially a (less functional, less clear) display output function like this:

Code:

function label_new_if_today($date, $date_format="Y-m-d", $label="(New Project)")
{
    return ($date === date($date_format)) ? $label : null;
}

being the developer of the FP library for PHP, i'm sure you are familiar with many of these arguments... but i'll lay out a few anyhow.

first of all, this function has a name - it should be clear to everyone who reads it. the string in the lam() function has to be studied to understand what it does.
second, it has parameters with defaults that are spelled out - what if i wanted to abstract that lam() function so that it could do a string compare on a different date format?
third, this function will be recorded in function_exists().

other issues...
there are many problems when you embed PHP code in a string - the most important immediate effect is that you lose the syntax.
you also lose the ability to reuse your function in another scope. the function is also hidden inside code.

in this case, defining a real function is better overall - i don't think you could convince anyone to adopt lambda functions to allow inline function creation based on string output function.

it seems to me that there must be a more compelling example for adopting FP than string output and concatenation...
maybe something that dramatically shifts the coding architecture?
some better way of working in teams, splitting up large problems?
making unit testing easier?
maybe there is a particular problem domain where FP is better suited? maybe an event-driven system?

sorry to be a pest, but you seem like a smart coder and i'd like to know what you are thinking.