A question about design. I've updated my update to the matrix extension by allowing the new map reporter primitive to take multiple matrices just as the NetLogo map primitive can take multiple lists. I've also added a map-in-place command primitive that replaces its single matrix argument with the new matrix. It would be trivial to allow map-in-place to take multiple matrices and to replace the first one in the list. But this makes me uneasy. It seems to me to be courting confusion and errors, and doing things in place seems out of keeping with most NetLogo primitives.
Any thoughts? Charles On Monday, February 17, 2014 4:24:08 PM UTC-5, Charles wrote: > > Seth's comment in Stack Overflow about the usefulness of a map primitive > in the matrix extension led me to add one, matrix:map task matrix. In the > process, I did some updating to use jama-1.0.3 rather than 1.0.2 and made > some minor non-substantive changes to the code to make my compiler happy. > I forked the original code off of the github NetLogo site to my own github > account, but now that I've made the changes, I'm not sure what to do next. > As a bundled extension I can't put it out there myself, and I assume that > even if the changes were useful for a large enough audience, there would be > a good bit of checking that you all would want to do. Indeed, I'm not > really clear on how I would push this back to you if it were useful. So, > I'm looking for advice on next steps, although if that is to just use it > myself, that's fine too. > > Charles > -- You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
