[erlang-questions] If you are homesick for object.selector
Sun Jan 27 10:46:21 CET 2013
On 01/27/2013 06:31 AM, Fred Hebert wrote:
> In the mean time, enjoy an implementation of it:
You're not fixing the issue, it still has no language support. In short
* Can't pattern match
* Can't use values with function clause guards
* Can't modify values at different depths in one go
Seems it's also quite verbose and you have to repeat paths all the time,
similar to how you have to repeat the record name all the time.
> And it lets you use any damn term you please for the path, not just yet
> another overloaded bunch of strings with encodings to worry about.
No idea what this means.
> On 01/25, Lo�c Hoguin wrote:
>> That's the point: it should be *built into the language*, you
>> shouldn't have to go through the trouble of doing something like
>> this. And it should be *obvious* and in line with the rest of the
>> language. I quite like the xpath idea Darach mentioned. It could
>> integrate very well with the rest of the language. I might
>> experiment with it.
>> Lo�c Hoguin
>> Erlang Cowboy
>> Nine Nines
More information about the erlang-questions