这限制了消息中的字符数,同时还指定将消息作为字符存储在数据库中。
This limits the characters in a message, as well as specifying that messages are stored in the database as characters.
问号表示无效选项,在这种情况下,触发它的字符存储在变量optopt中。
A question mark indicates an invalid option, in which case the character triggering it is stored in the variable optopt.
幸运的是,针对此问题有一个变通方法:我们将所有的特殊字符存储在引用源中,然后从那个源中装入,并在运行时使用它们。
Fortunately, there is a workaround to this problem: we store all the special characters in a reference source, load them from that source, and use them at run time.
It turns out when we call string a string, we're really referring not to those characters but to the address, the location and memory of those characters.
当我说字符串时,我并不是指这些字符集,而是指地址,就是这些字符集在存储器中的位置。
Well, get string again is returning the address of the string the user typed in, D the address of the very first character like the letter D and storing that address in this variable s1.
好的,GetString返回的是,用户输入的字符串的地址,第一个字符的地址,比如字母,然后把这个地址存储在这个变量s1中。
I'm going to delete that arrow and actually draw s2 as pointing to this chunk of memory because whereas before this sequence of chars might have lived at address 71 or whatever, well, this one might live at 91.
我不会把那个箭头删除,实际上我画了s2作为,这块内存的指针,因为,这个字符序列存储在地址71或其它的地方,这个可能存储在91的地方。
应用推荐