1 2017-03-23 00:44:00 <ProfMac> I submitted this RFQ:  https://bitcointalk.org/index.php?topic=1838719.new#new
 2 2017-03-23 13:52:22 <suryab> yo so i'm trying to patch the core client and get it to report inv messages that it sends out to the debug log
 3 2017-03-23 13:52:42 <suryab> so I'm trying to figure out how the core client deserialized the raw bytes of a message?
 4 2017-03-23 13:52:52 <suryab> it's a bit hard to understand directly from the code
 5 2017-03-23 13:58:24 <suryab> i should clarify deserialize into a message object
 6 2017-03-23 14:55:40 <achow101> suryab: you could just run core with debug=net
 7 2017-03-23 14:56:00 <suryab> does that dump messages to the debug log as well?
 8 2017-03-23 14:56:52 <achow101> with inv's I think it will say what it received or sent the inv for
 9 2017-03-23 14:57:00 <suryab> i thought that it only puts when, for example, an in message is sent or received
10 2017-03-23 14:57:10 <suryab> inv*
11 2017-03-23 14:57:32 <suryab> yeah it only tells you that an inv message is sent/received i don't think it actually logs the contents of that messgae
12 2017-03-23 14:57:53 <suryab> i'll try it now to make sure
13 2017-03-23 14:58:39 <achow101> I just checked. it does tell you for what
14 2017-03-23 14:58:51 <achow101> 2017-03-23 14:58:20 got inv: tx a61d6e40adbfeb3e25088b40a90e218dfd6294e25bf2ea8d73332176bdd76f0d  new peer=2
15 2017-03-23 14:58:51 <achow101> 2017-03-23 14:58:20 received: inv (325 bytes) peer=2
16 2017-03-23 14:58:51 <achow101> like this:
17 2017-03-23 14:59:18 <suryab> does it also tell you when it sends?
18 2017-03-23 14:59:26 <suryab> an inv
19 2017-03-23 14:59:47 <achow101> it should
20 2017-03-23 15:00:30 <achow101> my node is still syncing so I haven't gotten those messages yet
21 2017-03-23 15:22:51 <achow101> suryab: it doesn't seem to say what it is sending when it sends an inv message
22 2017-03-23 15:23:28 <suryab> yeah it's just '2017-03-23 15:23:07 sending inv (217 bytes) peer=8'
23 2017-03-23 22:55:22 <altsys> hi ! newbie question : anybody knows what means the C suffix in bitcoin core source code ? CBlock, CTransaction, etc...
24 2017-03-23 22:55:34 <altsys> why not just Block, Transaction, etc. ?
25 2017-03-23 22:55:43 <altsys> C prefix I mean
26 2017-03-23 23:13:56 <cncr04s> its just a prefix
27 2017-03-23 23:14:25 <cncr04s> doesnt really mean anything, other than its a product of the naming scheme of its devloper
28 2017-03-23 23:14:44 <cncr04s> like I may call stuff cncTimer
29 2017-03-23 23:15:00 <achow101> he left..
30 2017-03-23 23:15:06 <altsys> back
31 2017-03-23 23:15:20 <cncr04s> i answered you, you werent here
32 2017-03-23 23:15:51 <altsys> checking the logs
33 2017-03-23 23:16:31 <achow101> the C is arbitrary. I would guess that it stands for "Class" as in object, but it's arbitrary and doesn't matter
34 2017-03-23 23:17:12 <altsys> just curious
35 2017-03-23 23:17:41 <altsys> why bother prefixing, Block or Transaction would have done just fine, nope ?
36 2017-03-23 23:20:15 <achow101> organization maybe. all of the stuff prefixed with C are all for classes related specifically to Bitcoin itself. stuff not prefixed are for internal and other general functionality
37 2017-03-23 23:21:32 <altsys> ok thanks I understand now
38 2017-03-23 23:22:34 <altsys> coming from the smalltalk world, by convention classes are capitalize, but not the name of method
39 2017-03-23 23:22:58 <altsys> in bitcoin source code, it looks like method and classes are capitalized, so it makes sense to prefix classes with C
40 2017-03-23 23:25:23 <altsys> do you know if there is somewhere a UML classes diagram to figure out the relationship between classes ?
41 2017-03-23 23:35:00 <altsys> in bitcoin doc the end of money, we can see such a diagram at 42:22, does anyone know where does it come from ?
42 2017-03-23 23:44:48 <achow101> altsys: https://dev.visucore.com/bitcoin/doxygen/
43 2017-03-23 23:44:54 <achow101> or generate the doxygen docs yourself
44 2017-03-23 23:46:59 <altsys> thanks