• Oleg B (15/15) Feb 27 2017 Hello. Is this behavior normal, or it's a bug? And if it's normal
• Jonathan M Davis via Digitalmars-d-learn (6/21) Feb 27 2017 In your example, your module isn't in a package. It's at the top-level. ...

Oleg B <code.viator gmail.com> writes:

Hello. Is this behavior normal, or it's a bug? And if it's normal 
why it's normal? I want to use function with `package` visibility 
in same package where it's defined, but I don't.

```d
module package_visible;
package void foo() { }
void main() { foo(); }
```

```
% rdmd package_visible.d
package_visible.d(3): Error: function package_visible.foo is not 
accessible from module package_visible
Failed: ["dmd", "-v", "-o-", "package_visible.d", "-I."]
```

dmd version v2.073.1

Jonathan M Davis via Digitalmars-d-learn writes:

On Monday, February 27, 2017 14:07:21 Oleg B via Digitalmars-d-learn wrote:
 Hello. Is this behavior normal, or it's a bug? And if it's normal
 why it's normal? I want to use function with `package` visibility
 in same package where it's defined, but I don't.

 ```d
 module package_visible;
 package void foo() { }
 void main() { foo(); }
 ```

 ```
 % rdmd package_visible.d
 package_visible.d(3): Error: function package_visible.foo is not
 accessible from module package_visible
 Failed: ["dmd", "-v", "-o-", "package_visible.d", "-I."]
 ```

 dmd version v2.073.1

In your example, your module isn't in a package. It's at the top-level. So,
package doesn't work, becasue there's no package. In this case, you'd just
use private. Presumably, in any actual code, you would have a package rather
than putting the module at the top level, and then it would work.

- Jonathan M Davis