codedamn

Visibility

Created by Kshitij about a year ago

0

No description provided

10 Comments

    0

    This content was deleted by the author

    @madblock

    Android Guy

    @madblock

    0

    Confused, Y f4() is not able to access from the Derived contract (Child) ? in the table it's mentioned ad YES correct?

    @madblock

    Android Guy

    @madblock

    0

    Regarding Derived contract visibility, when u deploy Child contract, in the ide it shows f1,f4 , so that means those are the ones visible from the child correct ? if yes why f3 is not visible !!

    @madblock

    Android Guy

    @madblock

    0

    This video is confusing , slides and video are contradicting each other. Found this blog https://blog.oliverjumpertz.dev/solidity-visibility-modifiers . Hope it helps other learniners.

    @ltchitts

    Chitresh Kaushik

    @ltchitts

    0

    According to the table external functions can be accessed by derived contracts,so why was child not able to access f4?

    @harimenon0143

    Hari Menon

    @harimenon0143

    0

    Please correct this video.. External functions are accessible at child contract. But in video, it is showing error. Please see video at @5:10 sec..

    @averma475

    Abhishek Verma

    @averma475

    0

    A lot people mistaking visibility/accessibility and inheritance. Public and internal functions are visible/accessible by child contracts, private and external functions are not visible/accessible by them. Yet public, internal AND external functions are indeed inheritable by the child contracts. While an external function is not accessible by child, it still inherits the function.

    @egoceyo0595

    egoceyo

    @egoceyo0595

    0

    Sir, Can we use " external" in our Derived contracts? If the answer is yes, what is the reason to generate an error, when we use "f4() function" in our "child contract" ?

    @gayasha

    Pubudini Gayasha

    @gayasha

    0

    Sir once explain the syntax used in line 26 @6:30 time mark?

    @avinash572

    GORTI AVINASH

    @avinash572

    0

    It was a very easy explanation for a little bit complicated topic. Thanks Kshitij.

    @priyanshrai

    Priyansh Rai

    @priyanshrai

Your comment