#807: construction of function fields
------------------------------------+---------------------------------------
Reporter: nbruin | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: sage-5.8
Component: basic arithmetic | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
------------------------------------+---------------------------------------
Comment (by tscrim):
Replying to [comment:10 cremona]:
> No, not just you. And you probably also dislike this, as I do:
> {{{
> sage: y = polygen(QQ)
> sage: y
> x
> }}}
> This would be avoided by disallowing polygen()'s name parameter being
omitted (it defaults to "x"). After all we are not allowed to construct
number fields, or non-prime finite fields, without naming a generator, and
this is worse since we usually think that we have named a generator...
Yes I do not like that as well. However, even making name a mandatory
argument, it still does not prevent things such as:
{{{
sage: y = polygen(QQ, 'a')
sage: y
a
}}}
From looking at the function, I'd want to deprecate it if we decide to
forbid `R.<x> = QQ['t']` (which could be done in the preparse).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/807#comment:11>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
