|
Jacques Gélinas on Sat, 09 Mar 2019 22:58:46 +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: Sat, 9 Mar 2019 21:58:42 +0000
- Accept-language: fr-CA, en-US
- Delivery-date: Sat, 09 Mar 2019 22:58:46 +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=zguCBJEm9uLI06pABWkv/x+5e8zsnQ3OXEkoO31X/VU=; b=oPON+CSZrgAmxKDM+NcXWk308oPG1ol9uyrvDnxJALhlMi2leRdqr9nlGGMbjGx2sxhlGRIl++K88E7rZK1lfZt42N3YW9eKxzpku1WoKMwdyquRM57CiIvSXplPLqQrLG1KEiyHh3X5hzFVxvm3/Ur3pZzDaSYKpMiUCWVYxi0bn66/RACn7OMiICXub2D8mU8xz8TVCPfq2/sgKC9wQUP4B4Fa5vPXC5gtShKJF/+CgOPGrP4BWtx7TQYcGWqruYREEZQ1bG/p7oSMAHBzyABW69gSS128e0PU51/jXLEdIUf9bRXlsSXoEMsWfQN9D0xKnfF3Hp4DWozyaLPAkw==
- In-reply-to: <20190309093636.r7nocvd6u2cybtl7@math.u-bordeaux.fr>
- References: <YQXPR0101MB0885D2DDE015399E38FBFB8AD27E0@YQXPR0101MB0885.CANPRD01.PROD.OUTLOOK.COM> <CABcj=t=PFWeAg9rrEstFoU2LtY9omENkYboS0BFLu10rfbx+OA@mail.gmail.com> <CABcj=tnfMmfovJ3+UMBcAsuwvrwEoD7OHvE-oKbbhnisrAiX2g@mail.gmail.com> <YQXPR0101MB0885754448B3373BDBF112C8D27E0@YQXPR0101MB0885.CANPRD01.PROD.OUTLOOK.COM>,<20190309093636.r7nocvd6u2cybtl7@math.u-bordeaux.fr>
- Thread-index: AQHUyYWebVZUap3Lkkm8UcoUuVt9L6Xp44yAgAABSYCAAAYc7oAZOTEAgADMmBA=
- Thread-topic: poldisc variable must be x or y ?
> poldisc0(GEN x, long v) {
> case t_POL: { <====== oups!!! type(z/a+1)=="t_RFRAC" (:-(
$ poldisc(x/a+1)
1
$ poldisc(z/a+1) \\ variable "a" has higher priority than "z"
*** at top-level: poldisc(z/a+1)
*** ^--------------
*** poldisc: incorrect type in poldisc (t_RFRAC).
$ poldisc(z/a+1,z)
1
$ version
[2, 12, 0, 23659, "ad8d02474"]
Perfect! Thanks.
Jacques Gélinas