Hi everyone, Is it possible (and if yes what is t...

# announcements

[jtonic]

Hi everyone,

Is it possible (and if yes what is the best approach) of having classes with both package level visibility members and public members without internal and a new module?

public class Foo {
public void foo1() {}
void foo2() {}
}

public class Fee {
public void fee1() {}
void fee2() {}
}

[gildor]

But this is Java

[karelpeeters]

Doesn't is just work to mark some functions internal?

[jtonic]

Hi,
They are java but I wanted to emphasize what I would like to get in kotlin, all this w/o having a new module and internal visibility modifier.
As far as I understood having all classes as private in the same file doesn’t allow to have public members.

[karelpeeters]

I don't really undestand, you want private classes to have public fields? How would that every work?

[jtonic]

Hi Karel,

No, I don’t want private classes with public fields, I am wondering if package visibility from java has a corresponding in kotlin, but w/o using a internal and having a new module.
I really do not completely understand the reason behind not allowing this in kt. Java code.

module http
package http.dsl
public class Tag {
  public void add subTag()  {}
  void process() {}
}
package http.core
public class HttpBuilder  {

  public class build() {
   new Tag().addSubTag()
   new Tag().process() // does not compile, no autocomplete for it.
 }
}

[gildor]

package visibility from java has a corresponding in kotlin

Kotlin doesn’t have package visibility

[jtonic]

Thank you very much Andrey for the information.
But is there an approach to do what I am intending to do in Kotlin?
I am trying to convince my colleagues to use kotlin in production code (currently we are using it in tests) and this restriction combined with not being allowed to use late init for primitives (in fact in our case is the Integer wrapper) makes my colleagues/reviewers to step a bit back.

Thank you

Tony

[gildor]

I saw comment from Andrey Breslav, that Kotlin Team probably reconsider decision about package visibility.
For now you can use only internal + modules or keep code in the same file. None of them are direct replacement of course

[jtonic]

That will be great.
Thank you very much for the information and support.