Skip to content

Commit 7f2ae41

Browse files
committed
Update README with the non-truncation benefit of linkReferences
1 parent 211de4d commit 7f2ae41

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ bytecode = linker.linkBytecode(bytecode, { 'MyLibrary': '0x123456...' })
158158

159159
(Note: `linkBytecode` is also exposed via `solc` as `solc.linkBytecode`, but this usage is deprecated.)
160160

161-
As of Solidity 0.4.11 the compiler supports [standard JSON input and output](https://solidity.readthedocs.io/en/develop/using-the-compiler.html#compiler-input-and-output-json-description) which outputs a *link references* map. This gives a map of library names to offsets in the bytecode to replace the addresses at.
161+
As of Solidity 0.4.11 the compiler supports [standard JSON input and output](https://solidity.readthedocs.io/en/develop/using-the-compiler.html#compiler-input-and-output-json-description) which outputs a *link references* map. This gives a map of library names to offsets in the bytecode to replace the addresses at. It also doesn't have the limitation on library file and contract name lengths.
162162

163163
There is a method available in the `linker` module called `findLinkReferences` which can find such link references in bytecode produced by an older compiler:
164164

0 commit comments

Comments
 (0)