Calling injected function in same package files (returns undefined error) about gno HOT 2 CLOSED

@r3v4s the way that native imports are implemented are that when you import a package, ie. you write import "std", the gnovm loads the package's symbols, and on top of them some extra native bindings.

Notice that this means that native functions are only available to external users of the package; not from the package itself. This is one of the things I aim to improve/fix with #814.

For now, if you need to fix the bug, a good idea might be to extend stdlibs.go to go from case "std" to case "std", "internal/stdnative"; so that after that, calling GetOrigCaller becomes possible from banker.gno, by importing internal/stdnative.

from gno.

@r3v4s the way that native imports are implemented are that when you import a package, ie. you write import "std", the gnovm loads the package's symbols, and on top of them some extra native bindings.

Notice that this means that native functions are only available to external users of the package; not from the package itself. This is one of the things I aim to improve/fix with #814.

For now, if you need to fix the bug, a good idea might be to extend stdlibs.go to go from case "std" to case "std", "internal/stdnative"; so that after that, calling GetOrigCaller becomes possible from banker.gno, by importing internal/stdnative.

thx @thehowl, perhaps I have to stick with internal/stdnative for now.
I'll keep my eye open for your #814 :D

from gno.