Sorry, there should have been a period at the end of the sentence. Just the one explicitly stated. The function call still works, though it calls another, non-imported, function which is declared in the package. The importing or non-importing only affects the visibility of the names from the importing scope. So only the explicitly imported function name can be directly called from the importing scope, but the function, being defined within the package, can call another function which is also defined in the package. Shalom > -----Original Message----- > From: Korchemny, Dmitry > Sent: Tuesday, July 17, 2007 1:15 PM > To: Bresticker, Shalom; Lisa Piper; Eduard Cerny; > sv-ac@server.eda-stds.org > Subject: RE: [sv-ac] P1800: 1728 - formal proposal for Let Construct > > And what was his answer? > > Dmitry > > -----Original Message----- > From: owner-sv-ac@server.eda.org > [mailto:owner-sv-ac@server.eda.org] On Behalf Of Bresticker, Shalom > Sent: Tuesday, July 17, 2007 1:12 PM > To: Lisa Piper; Eduard Cerny; sv-ac@server.eda-stds.org > Subject: RE: [sv-ac] P1800: 1728 - formal proposal for Let Construct > > Just the one explicitly stated? > I had the same question, and asked Gord V. > > Shalom > > > > f) if I import a function from a package, and that function > references > > another function in that same package, are both functions > > automatically imported, or just the one explicitely stated? > > -- > This message has been scanned for viruses and dangerous > content by MailScanner, and is believed to be clean. > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Jul 17 03:20:35 2007
This archive was generated by hypermail 2.1.8 : Tue Jul 17 2007 - 03:20:45 PDT