| In my post Some way to validate proc refs, Lummox said: > hascall() always works with proc names, not proc references I …
|
|
0 |
|
|
|
3 |
|
|
|
28 |
|
|
| A much easier suggestion to implement would be a keyword that evaluates to the implied type at compile time, which you …
|
|
6 |
|
|
| I keep farting around and trying to make libraries for byond that nobody will ever use, and one of the ones I keep …
|
|
3 |
|
|
|
21 |
|
|
| I agree with this idea. Architecturally sometimes you want to grant/deny access to verbs in a packaged set; you can …
|
|
3 |
|
|
| Lummox JR wrote: > Nope. Let's say the var definition routine comes back with a flag that says it's a weak reference …
|
|
10 |
|
|
| Would it be feasible to only allow the syntax on typed variables in scope, eg, not allowing it to be used on untyped …
|
|
3 |
|
|
| The difference with non-supplied arguments is when they have defaults: proc/myproc(var/a="a",var/ b="b",var/c="c") …
|
|
6 |
|
|
| Fixed, sorry, I don't know why it did that
|
|
2 |
|
|
|
14 |
|
|
|
1 |
|
|
|
12 |
|
|
|
3 |
|
|
| I will not be surprised if the idea is ultimately rejected, it is a minor quibble compared to the work that would be …
|
|
12 |
|
|
|
0 |
|
|
