On 08.08.19 18:03, Drobet wrote:
Then why does it in the tour say that it can only be "seen by Integer"?
https://tour.dlang.org/tour/en/basics/classes
That's an error in the tour.
On Thursday, 8 August 2019 at 15:53:13 UTC, Zoadian wrote:
private means module private in D.
see: https://dlang.org/spec/attribute.html#visibility_attributes
Then why does it in the tour say that it can only be "seen by
Integer"?
https://tour.dlang.org/tour/en/basics/classes
On Thursday, 8 August 2019 at 15:51:45 UTC, Drobet wrote:
I'm having a weird issue, where after defining my classes
variables as private, they can still be modified and looked at
from the outside. That leads to this code compiling with no
issues.
[...]
My question is if this is intended
On Thursday, 8 August 2019 at 15:51:45 UTC, Drobet wrote:
I'm having a weird issue, where after defining my classes
variables as private
https://dlang.org/spec/attribute.html
Section 8.4.2 of the spec reads:
Symbols with private visibility can only be accessed from within
the same module.
On Thursday, 8 August 2019 at 15:51:45 UTC, Drobet wrote:
...
My question is if this is intended behavior, and if yes, why?
This is true if the class is inside the same module:
"Private means that only members of the enclosing class can
access the member, or members and functions in the same
I'm having a weird issue, where after defining my classes
variables as private, they can still be modified and looked at
from the outside. That leads to this code compiling with no
issues.
import std.stdio;
class Vector3
{
this(double _x = 0.0, double _y = 0.0, double _z = 0.0)
{
On Thursday, 8 August 2019 at 15:51:45 UTC, Drobet wrote:
I'm having a weird issue, where after defining my classes
variables as private, they can still be modified and looked at
from the outside. That leads to this code compiling with no
issues.
import std.stdio;
class Vector3
{
