View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000890 | LDMud 3.6 | LPC Language | public | 2021-04-12 09:24 | 2021-06-25 11:18 |
| Reporter | sinnvoll | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0000890: new string literal prefixes for ascii/unicode handling | ||||
| Description | There is now b"ForBytes" to get bytes a"AsciiOnly" would throw an error for NonAsciiChars introduced for example by script c"Maßstäbchen" would convert the string to Ascii at compile time | ||||
| Tags | No tags attached. | ||||
|
|
What is the use case behind the a""-Prefix? Why do you need a compiler error on non-ASCII-Strings? |
|
|
There are strings, that should be ascii file-names, user-names, tags for states I work with Search & Replace over many files. Sometimes I get it wrong. So I get an error, if something is wrong after a false replacement or a change of someone, who doesn't know it should be ascii. Compile Time Errors do trigger by loading the File without long testing. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-04-12 09:24 | sinnvoll | New Issue | |
| 2021-04-16 19:19 | Gnomi | Status | new => feedback |
| 2021-04-16 19:19 | Gnomi | Note Added: 0002594 | |
| 2021-04-16 19:48 | zesstra | Project | LDMud => LDMud 3.6 |
| 2021-06-25 11:18 | sinnvoll | Note Added: 0002655 | |
| 2021-06-25 11:18 | sinnvoll | Status | feedback => new |
