mirror of
				https://github.com/ethereum/solidity
				synced 2023-10-03 13:03:40 +00:00 
			
		
		
		
	resolve spelling issues in the docs folder
This commit is contained in:
		
							parent
							
								
									8825533222
								
							
						
					
					
						commit
						bf93665ad8
					
				| @ -171,7 +171,7 @@ Command Line and JSON Interfaces | ||||
|   the first 36 hex characters of the keccak256 hash of the fully qualified | ||||
|   library name, surrounded by ``$...$``. Previously, | ||||
|   just the fully qualified library name was used. | ||||
|   This recudes the chances of collisions, especially when long paths are used. | ||||
|   This reduces the chances of collisions, especially when long paths are used. | ||||
|   Binary files now also contain a list of mappings from these placeholders | ||||
|   to the fully qualified names. | ||||
| 
 | ||||
|  | ||||
| @ -597,7 +597,7 @@ Strict encoding mode is the mode that leads to exactly the same encoding as defi | ||||
| This means offsets have to be as small as possible while still not creating overlaps in the data areas and thus no gaps are | ||||
| allowed. | ||||
| 
 | ||||
| Usually, ABI decoders are written in a straigthforward way just following offset pointers, but some decoders | ||||
| Usually, ABI decoders are written in a straightforward way just following offset pointers, but some decoders | ||||
| might enforce strict mode. The Solidity ABI decoder currently does not enforce strict mode, but the encoder | ||||
| always creates data in strict mode. | ||||
| 
 | ||||
|  | ||||
| @ -43,7 +43,7 @@ | ||||
|     { | ||||
|         "name": "DelegateCallReturnValue", | ||||
|         "summary": "The low-level .delegatecall() does not return the execution outcome, but converts the value returned by the functioned called to a boolean instead.", | ||||
|         "description": "The return value of the low-level .delegatecall() function is taken from a position in memory, where the call data or the return data resides. This value is interpreted as a boolean and put onto the stack. This means if the called function returns at least 32 zero bytes, .delegatecall() returns false even if the call was successuful.", | ||||
|         "description": "The return value of the low-level .delegatecall() function is taken from a position in memory, where the call data or the return data resides. This value is interpreted as a boolean and put onto the stack. This means if the called function returns at least 32 zero bytes, .delegatecall() returns false even if the call was successful.", | ||||
|         "introduced": "0.3.0", | ||||
|         "fixed": "0.4.15", | ||||
|         "severity": "low" | ||||
|  | ||||
| @ -112,7 +112,7 @@ For example, you could run the following command in your ``build`` folder: | ||||
|    cmake -DCMAKE_BUILD_TYPE=Debug .. | ||||
|    make | ||||
| 
 | ||||
| This will create symbols such that when you debug a test using the ``--debug`` flag, you will have acecess to functions and varialbes in which you can break or print with. | ||||
| This will create symbols such that when you debug a test using the ``--debug`` flag, you will have access to functions and variables in which you can break or print with. | ||||
| 
 | ||||
| 
 | ||||
| The script ``./scripts/tests.sh`` also runs commandline tests and compilation tests | ||||
|  | ||||
| @ -171,7 +171,7 @@ As an exception, identifiers defined in the "init" part of the for-loop | ||||
| (the first block) are visible in all other parts of the for-loop | ||||
| (but not outside of the loop). | ||||
| Identifiers declared in the other parts of the for loop respect the regular | ||||
| syntatical scoping rules. | ||||
| syntactical scoping rules. | ||||
| The parameters and return parameters of functions are visible in the | ||||
| function body and their names cannot overlap. | ||||
| 
 | ||||
|  | ||||
		Loading…
	
		Reference in New Issue
	
	Block a user