From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-65-14.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,NICE_REPLY_A, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader01.eternal-september.org!news.szaf.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Niklas Holsti Newsgroups: comp.lang.ada Subject: Re: Text_io package's Positive_Count type Date: Wed, 11 Jan 2023 15:52:14 +0200 Organization: Tidorum Ltd Message-ID: References: <1ef161c8-8e65-4a82-8db8-c772e813be80n@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net E/3XXAGOr7OOn1G8x2i4ew5SsTW2VH36dwGITslteSRbamoEFv Cancel-Lock: sha1:HVEA9xjc4e65darTi1+a2BdYoJI= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Content-Language: en-US In-Reply-To: <1ef161c8-8e65-4a82-8db8-c772e813be80n@googlegroups.com> Xref: reader01.eternal-september.org comp.lang.ada:64795 List-Id: On 2023-01-11 12:14, Mace Ayres wrote: > I am using GNAT's,2018, GPS on 1 2012 Macbook Pro, Intel Chip, for > some Ada programming with IO to a terminal. I want to capture the > cursor position, row, and column with Text_IO line and col functions > returning to my variables of type Positive_count, declared in my > package's specification, *.ids file, Compile fails with an ambiguous > message about my line of code that calls line and col returning to > Postiive_count type variables. Please show the code that declares Positive_count, and the calls of Line and Col, and explain in which file they are located, and whether those files (or the corresponding .ads files) contain any "use" context-clauses. Showing the compiler's error message would also be helpful. Usually an ambiguity problem means that there are several different subprograms with the same name, and the compiler does not know which one you want to call, because the types of the parameters and the result are not sufficiently constraining, or because the call does not qualify the subprogram name with a package name.