Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/18/2016 in all areas

  1. Theres some interesting additions -- I like the built-in sorting and filtering idea -- but one thing I can't get past, and its the issue with every error improvement I've seen, is that it still doesn't really work with the standard error cluster since you pass around arrays rather than the base cluster. Its not compatible anyway without adding a node to convert between them, it seems like making bigger changes is appropriate. Edit: thinking about Shaun's q below, the versions I've seen seem to be either (a) not the same data type or (b) the same 'type' but used in a fragile way. In both cases you have to isolate either (a) your new data type or (b) your carefully crafted 'source' string from the errors provided by built-in functions or functions in most any other library. And doing this conversion is itself a challenge as theres a billion different error generators -- code to error function with or without various options, stephen's xnode, and the custom ones built by a lot of different groups. Its quite a challenge to convert these various data types and honestly I think its more challenging to deal with the variety of ways the standard cluster is used. Maybe I'm missing something, thats the impression I've gotten.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.