ツイート
会話
i think it’s more of a shitpost than an argument
38
返信先: さん, さん
And if you started with BASIC, you expect strings to have $ at the end of their variable name; if you started with Pascal you expect them to be limited to 255 single-byte characters and have the length in byte 0.
1
I started with Turbo Pascal and no, I do not expect a string to be represented Pascal-style and I'd further suggest that date storage and math is a much bigger issue than string representation.
2
Forever C/C++
1
返信先: さん
Not sure this is a good thing. I wonder if you switched the before and after column if Rust fan-people would still post it. I suspect they would.
2
1
Why do you suspect that? Do you think that we don't know our own language?
4
wchar_t*
const wchar_t*
char8_t*
const char8_t*
char16_t*
const char16_t*
char32_t*
const char32_t*
std::basic_string<CharT, Traits, Allocator>
std::basic_string_view<CharT, Traits>
std::vector<T>
std::span<T, Extent> // T can also be const here
std::filesystem::path
And so on.
1
10
path and pathbuf not really, because they allow you to do things unique to paths like convert them to absolute, join paths with the correct separator, do file operations with them, etc. osstring makes no sense until you target windows
1
7
返信を表示
返信先: さん
idk what you're talking about we had these 20 years ago
CString
BSTR
CComBStr
UNICODE_STRING
WCHAR wPath[MAX_PATH+MAYBE_ONE_IDK];
std::basic_string<TCHAR>
std::string
std::wstring
3
4
31
Plus the plethora of ways to talk about string pointers in Win32, and infinite forum questions about "how do I convert a char * to LPC?[TW]?STR"?
8
URLs are in an external crate and not part of the standard library.
返信先: さん
Cocoa:
NSString -> Human readable, Unicode
NSData -> a bunch of bytes, do what you will
1
5
メディアを再生できません。
再読み込み
1
Twitterを使ってみよう
今すぐ登録して、タイムラインをカスタマイズしましょう。
Googleアカウントでサインイン
電話番号またはメールアドレスで登録