From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 37368 invoked by alias); 17 Sep 2017 14:45:43 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 37251 invoked by uid 89); 17 Sep 2017 14:45:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=kawasourcewareorg, kawa@sourceware.org, U*kawa, H*x:8.5 X-HELO: homiemail-a23.g.dreamhost.com Received: from sub3.mail.dreamhost.com (HELO homiemail-a23.g.dreamhost.com) (69.163.253.7) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 17 Sep 2017 14:45:12 +0000 Received: from homiemail-a23.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a23.g.dreamhost.com (Postfix) with ESMTP id C42B74B0063; Sun, 17 Sep 2017 07:45:07 -0700 (PDT) Received: from vereq.eip10.org (cpe-74-75-122-130.maine.res.rr.com [74.75.122.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: chaw@eip10.org) by homiemail-a23.g.dreamhost.com (Postfix) with ESMTPSA id A423F4B0062; Sun, 17 Sep 2017 07:45:07 -0700 (PDT) Received: from chaw by vereq.eip10.org with local (Exim 4.84_2) (envelope-from ) id 1dtaod-0001gk-TH; Sun, 17 Sep 2017 10:44:59 -0400 To: Sonny To cc: Kawa mailing list Subject: Re: warning when invoking method on java object From: "Sudarshan S Chawathe" Reply-To: "Sudarshan S Chawathe" In-reply-to: Your message of "Sun, 17 Sep 2017 07:34:11 -0700." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <6492.1505659499.1@vereq.eip10.org> Date: Sun, 17 Sep 2017 14:45:00 -0000 Message-ID: <6493.1505659499@vereq.eip10.org> X-IsSubscribed: yes X-SW-Source: 2017-q3/txt/msg00046.txt.bz2 I have found that declaring the types of a few key variables and procedures (using the ::footype syntax) usually gives the type-inferencing engine enough information to infer the needed types for the remaining variables (typically generated from the earlier ones by applying Java methods) and avoid the warnings. Regards, -chaw > From: Sonny To > Date: Sun, 17 Sep 2017 07:34:11 -0700 > Subject: warning when invoking method on java object > To: Kawa mailing list > > (context:startActivity i) > > gives a warningi > /dev/stdin:23:2: warning - no known slot 'startActivity' in java.lang.Object > > it works but why is it giving a warning? > > I could do > ((as android.app.Application context):startActivity i) > > and not get a warning but its more verbose. what is more idiomatic? I > prefer the former but I am concern about getting warnings. >