Difference between revisions of "User:Inutt/CodingIdeas"
From Flexible Survival
(use/+use) |
(Reasons) |
||
| Line 7: | Line 7: | ||
</div> | </div> | ||
| − | * Add prop to players that have womb/other private rooms so they can be found without looping through all room objects | + | * Add prop to players that have womb/other private rooms so they can be found without looping through all room objects - it would just make more sense and improve efficiency |
| − | * Write a parameter checking function - basically an improved <code>checkargs</code> | + | * Write a parameter checking function - basically an improved <code>checkargs</code> to highlight more clearly when incorrect parameters are passed |
** Check number of supplied parameters is actually on the stack | ** Check number of supplied parameters is actually on the stack | ||
** Check type of arguments | ** Check type of arguments | ||
| Line 17: | Line 17: | ||
*** If top of stack matches type, add to dict of parameters by name | *** If top of stack matches type, add to dict of parameters by name | ||
* Unify <code>use</code> and <code>+use</code> | * Unify <code>use</code> and <code>+use</code> | ||
| + | * Merge/replace hasBoxItem with findBoxItem - they both seem to do the same thing | ||
| + | ** hasBoxItem returns 0 or 1 | ||
| + | ** findBoxItem returns the slot the item is found in or 0 | ||
| + | ** findBoxItem could therefore be used for any binary checks that hasBoxItem is currently used for | ||
Revision as of 05:05, 20 August 2019
Coding ideas
Please note: These are just ideas that I've had and are not necessarily well thought out, are in no particular order, have no guarantee of ever actually happening, may be either impossible or inadvisable, and may contain nuts.
- Add prop to players that have womb/other private rooms so they can be found without looping through all room objects - it would just make more sense and improve efficiency
- Write a parameter checking function - basically an improved
checkargsto highlight more clearly when incorrect parameters are passed- Check number of supplied parameters is actually on the stack
- Check type of arguments
- Something like
"str:foo int:bar dbref:baz any:qux" checkparams- Check stack depth
- Split on ' ' and foreach in reverse order
- Split on ':' into type,name
- If top of stack matches type, add to dict of parameters by name
- Unify
useand+use - Merge/replace hasBoxItem with findBoxItem - they both seem to do the same thing
- hasBoxItem returns 0 or 1
- findBoxItem returns the slot the item is found in or 0
- findBoxItem could therefore be used for any binary checks that hasBoxItem is currently used for
