首页 \ 问答 \ 在C ++中，* function（arguments ..）和function（arguments）之间有什么区别？(In C++ what is the difference between *function(arguments..) and function(arguments))

在C ++中，* function（arguments ..）和function（arguments）之间有什么区别？(In C++ what is the difference between *function(arguments..) and function(arguments))

 我看到了类型的功能：  
data_type *function_name(arguments...)
 
 和：  
data_type function_name(arguments...)
 
 我正在努力了解应该使用哪一个。 为什么在下面的例子中完成？ （这是来自课程的教科书。）我什么时候应该写这些函数？  
struct Tower
{
    string name;
    Tower *link;
};

Tower *createTower(string name, Tower *link);
 
 有人可以澄清一下吗？  
Tower* createTower(string name, Tower *link)
{
    Tower* tp = new Tower;
    tp->name = name;
    tp->link = link;
    return tp;
}

Tower* createBeconsOfGondor(){
    Tower *tp = createTower("Rohan", NULL); // Points to nothing
    tp = createTower("Halifiren", tp); // Still returns pointer?
}
 
 在createBeconsOfGondor（）函数的第二行，该函数的返回如何仍然是一个指针？ 

I see functions of the type: 
data_type *function_name(arguments...)
 
and: 
data_type function_name(arguments...)
 
I'm trying to learn when which one should be used. Why is this done in the example below? (This is from a textbook for a course.) When should I write functions like these? 
struct Tower
{
    string name;
    Tower *link;
};

Tower *createTower(string name, Tower *link);
 
Further can someone clarify this? 
Tower* createTower(string name, Tower *link)
{
    Tower* tp = new Tower;
    tp->name = name;
    tp->link = link;
    return tp;
}

Tower* createBeconsOfGondor(){
    Tower *tp = createTower("Rohan", NULL); // Points to nothing
    tp = createTower("Halifiren", tp); // Still returns pointer?
}
 
In the second line of the createBeconsOfGondor() function, how is the return of that function still a pointer?

原文：https://stackoverflow.com/questions/30491666

更新时间：2023-12-09 13:12

最满意答案

 你说比特币地址不应该被重用是对的。  
 比特币私钥只有一个公钥，但它可以是不同的格式，压缩或未压缩。 例如，私钥e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855  
 有一个相应的未压缩公钥04a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd5b8dec5235a0fa8722476c7709c02559e3aa73aa03918ba2d492eea75abea235  
 和压缩的公钥03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd  
 对它们进行散列将分别产生地址1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN和1F3sAm6ZtwLAUnj7d38pGFxtP3RVEvtsbV 。  
 您应该只使用压缩的公共密钥作为未压缩的公钥，膨胀区块链。 话虽如此，因为您只应将其中一个地址用于私钥，这意味着您还应该为每个事务使用不同的私钥。 现在这会产生许多其他问题，例如密钥管理会变得更加麻烦，因为每次要进行事务时都必须生成新的私钥。 您应该查看分层确定性钱包，因为这是一个旨在处理其中一些问题的建立标准。 

You are correct in saying that bitcoin addresses should not be reused.  
A bitcoin private key only has one public key, but it can be in different formats, compressed or uncompressed. For example, the private key e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 
has a corresponding uncompressed public key of 04a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd5b8dec5235a0fa8722476c7709c02559e3aa73aa03918ba2d492eea75abea235 
and a compressed public key of 03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd 
Hashing them will result in the address 1HZwkjkeaoZfTSaJxDw6aKkxp45agDiEzN and 1F3sAm6ZtwLAUnj7d38pGFxtP3RVEvtsbV respectively.  
You should only use compressed publics keys as uncompressed public keys bloat the blockchain. That being said, since you should only use one of those address for a private key, that means you should also use a different private key for every transaction. Now this creates a host of other problems, like key management becomes a lot more troublesome since you have to generate a new private key every time you want to do a transaction. You should look into hierarchical deterministic wallets as that is an establish standard that is meant to deal with some of these issues.

在C ++中，* function（arguments ..）和function（arguments）之间有什么区别？(In C++ what is the difference between *function(arguments..) and function(arguments))

最满意答案

相关问答

如何使用R包'hash'访问R中的整数键(how to access integer keys in R using R package 'hash')[2022-10-29]

多个公钥PKI包[R](Multiple Public Keys PKI Package [R])[2023-09-22]

Python中的ECC - 加密到多个公钥？(ECC in Python--Encrypt to Multiple Public Keys?)[2023-05-05]

为什么这些Botan公钥如此相似？(Why are these Botan public keys so similar?)[2022-03-01]

在PKI中，如果每个人都知道公钥，那就意味着任何人都可以解密......？(In PKI if everyone knows the public key does it mean anyone can decrypt …?)[2023-05-14]

公钥/私钥中的RSA密钥值和模数(RSA Key Values and Modulus in Public/Private Keys)[2022-03-30]

与公钥和私钥以及JWT有关的混乱(Confusion relating to public and private keys and JWT)[2023-10-18]

在Powershell中对Windows Server 2012 PKI进行身份验证(Authentication in Powershell to windows server 2012 PKI)[2023-06-17]

如何使用Hadley的安全包正确设置密钥(How to correctly setup keys with Hadley's secure package)[2023-09-18]

为什么Hadoop使用Kerberos而不是PKI / OAuth进行身份验证？(Why Hadoop uses Kerberos instead of PKI/OAuth for authentication?)[2022-03-06]

相关文章

最新问答