I don't think we need "copy" keyword

[yegor256]

Looks like copy keyword is redundant. I'm suggesting this:

type Point:
  Point moveTo(int x, int y)
object cursor(0, 0) as Point:
  Number @x
  Number @y
  Point moveTo(int x, int y):
    cursor: # here we COPY an object
      plus: @x, x
      plus: @y, y

No need to use copy at all. Just type and object are the keywords we need. What do you think?

[DronMDF]

I do not understand how to create a number of different objects of the same type.

type Person:
    ....
object yegor256 as Person:
    ...
object dron as Person:
    ...

dron is not a copy of yegor256...

[yegor256]

@DronMDF you create one object first, and call it, say somebody. Then, you copy yegor256 and dron from it:

type Person:
    ....
object somebody("noname") as Person:
    ....
yegor256("Yegor Bugayenko")
dron("Andrey Valyaev")

See?

[DronMDF]

Where is specified, that yegor256 it is Person or copy of somebody?

yegor256("Yegor Bugayenko")

somebody is ok.
object somebody("noname") as Person:

But all behavior inside of somebody.
yegor256 is specific version of somebody.. Is where it write?

[yegor256]

@DronMDF I didn't understand the question(s). Can you re-write the first one again please?

[DronMDF]

Sorry. :(

yegor256("Yegor Bugayenko")

Is where object type? How can i find it?

Another example:
string("Hello, world!")

What is the "string"? Type, object or object instance name? I can't understand.

[mdbs99]

@yegor256 and @DronMDF
The first syntax is wrong.
What about this?

type Person:
    ....
object somebody("noname") as Person:
    ....
object yegor256("Yegor Bugayenko") from somebody
object dron("Andrey Valyaev") from somebody

[mdbs99]

About string I suggest this:
object str("Hello, world!") as String

[DronMDF]

@mdbs99:
Where prototype?

object hello("Hello, world!") from string

[mdbs99]

@DronMDF you're right.
So, another syntaxe, a little bit different:

type String:  // a built-in type
...
object string as String
object hello("Hello, world!") from string

The "prototype" will be string, ie, an object that implements String.

[DronMDF]

Hello world example should be look differ.

[mdbs99]

@DronMDF I think so.

@yegor256 what do you think?

[nqafield]

@mdbs99 Yeah, I'm not exactly sure I follow what's going on with all of this. I don't understand Yegor's comment/example above. I would've expected something like this:

type Person:
    ....
create person("noname") as Person:
    ....
yegor256 = person("Yegor Bugayenko")
dron = person("Andrey Valyaev")

Except that there doesn't appear to be a need for "variables" in this scheme, so he can't have meant exactly that.
(I'm catching up on lots of reading of issues and comments at the moment so that's the best I can do.) :)

[yegor256]

hey guys, we won't have variables, keep this in mind!

[yegor256]

@pa9ey please, review the latest version of README, I've made many changes a few minutes ago

[DronMDF]

type Person:
    ....
person("anonymous") as Person:
    ctor(String name)

And later, names is not need. No variables! Ok.

person: "Yegor"
person: "Andrey"

Or

person: string: "Yegor"
person: string: "Andrey"

I'ts right syntax?
string is need? Or is this implicit?

[yegor256]

@DronMDF that's a good question about String, I will explain it now in README

[yegor256]

No copy keyword any more, I'm closing this ticket