| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame^] | 1 | SYNOPSIS |
| 2 | int save_ed_setup(object who, int code) |
| 3 | |
| 4 | DESCRIPTION |
| 5 | Save individual option settings of the builtin ed, encoded |
| 6 | into code, for the user denoted by who. These functions are |
| 7 | located in the master object so that the local gods can decide |
| 8 | what strategy they want to use. suggestions: |
| 9 | A setup file for every user. |
| 10 | advantages: transparent to the user |
| 11 | independent of user count |
| 12 | disadvantage: extra file access at ed invocation |
| 13 | An array in the master object, users are searched by member_array |
| 14 | advantage: easy to implement |
| 15 | disadvantage: performance degradation with high user counts |
| 16 | An AVL-tree to access users by name |
| 17 | advantage: can fit any need |
| 18 | disadvantage: hard to implement, will need more |
| 19 | overhead on small and medium |
| 20 | installations than it can ever make |
| 21 | good by lg(usercount) complexity |
| 22 | Dedicated flags in every user object. |
| 23 | advantages: easy to implement |
| 24 | independent of user count |
| 25 | Will also work for nusers w/o file |
| 26 | access privileges. |
| 27 | disadvantage: care has to be taken to avoid |
| 28 | collision with other uses of the flags |
| 29 | in the user object |
| 30 | |
| 31 | SEE ALSO |
| 32 | ed(E), retrieve_ed_setup(M), valid_write(M), |
| 33 | get_ed_buffer_save_object_name(M) |