On Friday, February 5, 2016 at 6:43:38 AM UTC-8, Nathann Cohen wrote: > > Let me add to that: > > sage: Matrix(whatever=58) > [] > Yes, this is a more universal problem in the UI: it's quite common that unknown keywords just get pass through, usually because they might be of use for a constructor further up in the inheritance tree or because some routine further down hasn't removed it. I can see why it's more efficient, more flexible, and easier to program it this way, but it ends up giving very poor error reporting in the UI. Maple, for instance (which otherwise has very poor error reporting), does a pretty good job on giving informative errors quickly about unrecognized options. It made it much more pleasant to work with if you're not 100% familiar with the system.
It would be nice if we can find an easy to use, low (zero?) overhead way of getting better checking on unknown keywords. I don't have a solution (python definitely seems to invite the lax way we're doing it) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
