 | | Re: markup syntax for member pages
|
|
Update: Here's some sample input/output going down one currently-favored path... The details of the content in this sample aren't important (it's just a personal e-mail with some ramblings) but the makeup of it is important... I wanted to grab (...) (27 years ago, 7-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
A far easier numbering system would be to use segments, ie an ID could be made up of subparts that could be used for future Lugnet marketing purposes, give aways and localised promotions. For instance the segments could include: Country of Origin, (...) (27 years ago, 7-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: markup syntax for member pages
|
|
(...) I don't quite grok. By COBOL-style comments do you mean something in column 1 affecting the rest of the line? And if so, why do you feel it is bad to mix that with paired (open/close) constructs? Take C++ for example -- it offers two types of (...) (27 years ago, 7-Jul-99, to lugnet.admin.general, lugnet.off-topic.geek)
|
| |
 | | Re: Allocation of member #'s
|
|
I agree with Ed on this one....if people start using arguments like who posted the first post or who argued the first argument or who boobed with the first blooper then things will really get out of hand. An easier option, one that will guarantee to (...) (27 years ago, 7-Jul-99, to lugnet.admin.general)
|
| |
 | | Re: Allocation of member #'s
|
|
(...) No, that's right. If people get the number they want, that's really great. But if they don't, I don't really care (much). But I *do* care (a lot) that people be given the choice to -avoid- certain numbers that they don't want. That is, I would (...) (27 years ago, 7-Jul-99, to lugnet.admin.general)
|