mirror of
https://github.com/evennia/evennia.git
synced 2026-03-16 21:06:30 +01:00
fix #2549 -- no reuse BIF names
- fixed docs to not demonstrate reuse of built-in function names "str" and "int", even when within a one-off script - note: did *not* change the "str" and "int" shown in Howto/Starting/Part1/Learning-Typeclasses.md file, as those are class variables (i.e., Character.str and Character.int), which does not replace the BIFs of str() and int(). Therefore, methods inside the class can still use the python BIFs. While this is possibly confusing to new python programmers, it is also not within the scope of #2549. misc edits: - add .vscode/ to gitignore
This commit is contained in:
parent
798fb7d92d
commit
e98ea55d98
2 changed files with 5 additions and 2 deletions
|
|
@ -128,7 +128,7 @@ instead.
|
|||
Here's the stat-example again, moving the stats to variables (here we just set them, but in a real
|
||||
game they may be changed over time, or modified by circumstance):
|
||||
|
||||
> py str, dex, int = 13, 14, 8 ; print("STR: {}, DEX: {}, INT: {}".format(stren, dex, int))
|
||||
> py stren, dex, intel = 13, 14, 8 ; print("STR: {}, DEX: {dex}, INT: {}".format(stren, dex, intel))
|
||||
STR: 13, DEX: 14, INT: 8
|
||||
|
||||
The point is that even if the values of the stats change, the print() statement would not change - it just keeps
|
||||
|
|
@ -148,7 +148,7 @@ An f-string on its own is just like any other string. But let's redo the example
|
|||
We could just insert that `a` variable directly into the f-string using `{a}`. Fewer parentheses to
|
||||
remember and arguable easier to read as well.
|
||||
|
||||
> py str, dex, int = 13, 14, 8 ; print(f"STR: {str}, DEX: {dex}, INT: {int}")
|
||||
> py stren, dex, intel = 13, 14, 8 ; print(f"STR: {stren}, DEX: {dex}, INT: {intel}")
|
||||
STR: 13, DEX: 14, INT: 8
|
||||
|
||||
We will be exploring more complex string concepts when we get to creating Commands and need to
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue