[KissLick]

Ciao guys,

can you please explain me, how does this work (taken from datapack.inc)?

PHP Code:

methodmap DataPack < Handle
{
    public WriteCell() = WritePackCell;
}; 


What confuses me is, that on official API site the DataPack.WriteCell method looks like:

PHP Code:

void WriteCell(Handle pack, any cell) 


But as far as I understand it should look like this

PHP Code:

void WriteCell(any cell) 


So, how does this "alias" method definition work?
I assume that the metod just inherits the exact arguments from it's "parental" function, but what about that Handle arg?
Shouldn't it be something like bellow to exactly set the arguments and say, what argument is used as the object we are calling the method on?

PHP Code:

methodmap DataPack < Handle
{
    public WriteCell(any cell) = WritePackCell(Handle this, any cell);
}; 


[WildCard65]

The way DataPack is doing it is no longer valid in 1.8, basically, what is doing is mapping WriteCell to WritePackCell(so when the compiler finds any WriteCell(any cell) it replaces it with WritePackCell(<Handle before the ".WriteCell">, <Value in "()" of "WriteCell">);
ex:

PHP Code:

DataPack dp = new DataPack();
dp.WriteCell(5); 


becomes:

PHP Code:

DataPack datapack = CreateDataPack();
WritePackCell(datapack, 5); 


[Powerlord]

You should probably file a bug against the documentation generator.

Basically, when the doc generator runs across public WriteCell() = WritePackCell; it needs to be aware that WriteCell will not have WritePackCell's first argument as it's implicitly the DataPack itself.

[WildCard65]

Originally Posted by Powerlord You should probably file a bug against the documentation generator. Basically, when the doc generator runs across public WriteCell() = WritePackCell; it needs to be aware that WriteCell will not have WritePackCell's first argument as it's implicitly the DataPack itself.

Atm, yes the bug can cause confusion, but eventually, the bug will be irrelevent as eventually it will no longer be valid to do what DataPack is doing in 1.7

[Powerlord]

Originally Posted by WildCard65 Atm, yes the bug can cause confusion, but eventually, the bug will be irrelevent as eventually it will no longer be valid to do what DataPack is doing in 1.7

This is the first I've heard of this syntax being deprecated. Any source for this?

Incidentally, said syntax is still being used in the MethodMap section of the transitional guide.

[Miu]

https://forums.alliedmods.net/showthread.php?t=269895

[WildCard65]

Originally Posted by Powerlord This is the first I've heard of this syntax being deprecated. Any source for this? Incidentally, said syntax is still being used in the MethodMap section of the transitional guide.

It's still valid syntax in SM 1.7, it's just SM 1.8 and greater that it's invalid in.

[KissLick]

Damn! I missed that one!

I even added binding support to docparser and docgen... :-D :-D Now that is obsolete...

[BAILOPAN]

Yeah, sorry that that led you down a dead end. The syntax was confusing and very difficult to support in the parser, so it got removed.