|
Jacques Gélinas on Thu, 21 Feb 2019 10:03:32 +0100
|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
RE: poldisc variable must be x or y ?
|
- To: "pari-users@pari.math.u-bordeaux.fr" <pari-users@pari.math.u-bordeaux.fr>
- Subject: RE: poldisc variable must be x or y ?
- From: Jacques Gélinas <jacquesg00@hotmail.com>
- Date: Thu, 21 Feb 2019 09:03:29 +0000
- Accept-language: fr-CA, en-US
- Delivery-date: Thu, 21 Feb 2019 10:03:32 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=QLIRbVB6UiQUtIC2zARkoARlBYF2eZaOy3v+Ue2IQdM=; b=Zj16eODuXVJg230m89itX87jcjfkvmdkNdQlrOiy+d8LYhTVZrQ2KOZRmjwJhuvPnoSk5nOo0dzcqLoeFS/vMa+RH/DJ5bBDRehH2IYnHulcChphP8HDY5kO2399/egceMqw6sHfDBIy9irOpphaj7dcyZdg1pb9dxsGAH3CEOdhtT6F5Q0MtqW+RXp4mvnwKWCFmWlKYyaTvyg/K9hizU2iGwftTu7RPU8H6Zhzd6rPKhulg1bmcYD0VxO3bq2qiqHmuPLm/f8LCmtS0i09cU5N2cs+KCYFrrFN+lU9Ynuo2sXpEgx9yOmLGb4CVqCG1U5TTx7Qvw/V0j/TqXNRkw==
- In-reply-to: <CABcj=tnfMmfovJ3+UMBcAsuwvrwEoD7OHvE-oKbbhnisrAiX2g@mail.gmail.com>
- References: <YQXPR0101MB0885D2DDE015399E38FBFB8AD27E0@YQXPR0101MB0885.CANPRD01.PROD.OUTLOOK.COM> <CABcj=t=PFWeAg9rrEstFoU2LtY9omENkYboS0BFLu10rfbx+OA@mail.gmail.com>,<CABcj=tnfMmfovJ3+UMBcAsuwvrwEoD7OHvE-oKbbhnisrAiX2g@mail.gmail.com>
- Thread-index: AQHUyYWebVZUap3Lkkm8UcoUuVt9L6Xp44yAgAABSYCAAAYc7g==
- Thread-topic: poldisc variable must be x or y ?
Thanks for the confirmation of the variable order problem.
So what is the use of the second argument v in poldisc ?
poldisc0(GEN x, long v) {
case t_POL: { <====== oups!!! type(z/a+1)=="t_RFRAC" (:-(
long v0 = -1;
if (v >= 0 && v != varn(x))
{
v0 = fetch_var_higher();
x = fix_pol(x,v, v0);
}
D = RgX_disc(x);
The easy fix is to always use x or y as main variable.
Jacques Gélinas