Re: [sbml-arrays] Infix syntax for arrays

[Chris J. M. <my...@ec...>]

Seems a reasonable point to me.  I was not keen on allowing A[i,j] as well as A[i][j], but assuming we do, it does seem like it would be nice to get that back when you parse as well.  I always found it a bit odd when you have aliases for things because you don't get back what you typed in.

Chris

On Apr 8, 2014, at 1:23 AM, Sarah Keating <ske...@ca...> wrote:

> 
>>> I would be okay if:
>>> 
>>> A[i][j] compiles to selector(selector(A,i),j) and A[i,j] compiles to selector(A,i,j).
>>> 
>>> However, if we make that change, then I would prefer that A[i,j,k] is illegal.  Instead, you must either do:
>>> 
>>> A[i][j][k] OR A[i,j][k] OR A[i][j,k]
> 
> I agree.
> 
> My point was really not to do with creating invalid (or indeed ambiguous 
> stuff) but was focussed on the point that one of the thinks the new 
> parser allowed (which was a good beneficial thing) was for the user to 
> get what they put in rather than a libsbml imposed version of what they 
> entered.
> 
> It just seemed to me that by saying that A[i,j] would become a nested 
> selector equivalent to A[i][j] we were going back on this principle :-)
> 
> Sarah
> 
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment 
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> sbml-arrays mailing list
> sbm...@li...
> https://lists.sourceforge.net/lists/listinfo/sbml-arrays