301 reputation
110
bio website
location Porto Alegre, Brazil
age
visits member for 3 years, 8 months
seen May 24 at 22:57

May
18
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
I see, that makes sense!
May
18
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
This sounds similar to the Proxy pattern mentioned by @Shmoken, doesn't it?
May
14
awarded  Popular Question
May
14
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
@ThePopMachine I agree the word "nobody" might be too hard in this case, but Employee examples are found by the dozens, either online or in classic books, while I haven't seen EmployeeInfo yet (perhaps because an employee is a living being, not a technical construct like a connection or a file). But, agreed, if the class EmployeeInfo were to be proposed in a project, I believe it could have its use.
May
14
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
(continued...) that is: I don't talk to the sensors themselves, I talk only to the Receiver via higher-level commands, and the Receiver in turn talks to each of the Sensors. But I eventually need information from the sensors, which I get from the Receiver instance via its List<SensorInfo> readonly property.
May
14
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Excellent. Earlier today I was analyzing my architectural needs, regarding the classes I used in the question, and came to this very same conclusion. In my case, I have a Receiver which receives data streams from many Sensors. The idea is: the receiver should abstract the actual sensors. But the problem is: I need the sensor info so that I can write them to some file header. The solution: each IReceiver will have a list of SensorInfo. If I send commands to the receiver which imply changing sensor state, these changes will be reflected (via getter) on the respective SensorInfo.
May
13
awarded  Nice Question
May
13
comment Data format for binary data transfer
Edf is just mentioned as a starting point, of course its useful ideas can be applied without its rather artificial limitations. @jbcolmenares, anything that changes between consecutive frames should be encoded in each frame, I think, so I would suggest you to create a field in your frame to describe sensor configuration for that frame. Alternatively, you could have something like segments, that is, you have a handshake, then write the start of a segment (with some parameters, then a datastream, then an end-of-segment marker, then another start of segment...
May
12
comment Data format for binary data transfer
What programming language/environment are you using?
May
12
comment Data format for binary data transfer
The idea would not stream the header, but only use its content for "handshaking" between oscilloscope and probe before streaming starts. Then, when you stream, you stream only the raw part, composed of a sequence of frames, each frame containing the appropriate amount of samples from each probe.
May
12
answered Data format for binary data transfer
May
10
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Again, kudos for the "glorified struct" part :) . That reminds me of a related quote from Uncle Bob's "Clean Code" book, Chapter 6: "Mature programmers know that the idea that everything is an object is a myth. Sometimes you really do want simple data structures with procedures operating on them."
May
9
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Thanks for your answer, and kudos for your "have-a" construct ;) Your answer reminds me of the discomfort caused on some by the "DTO" (Data Transfer Object) concept - or its sibling the Parameter Object - which is frowned upon by more orthodox OO zealots because it usually does not contain methods (after all it is a data transfer object). In that sense, and summarizing also what others have said, I think the SensorInfo would be sort of a DTO, and/or also like a "snapshot", or even a "spec", representing only the data/state part of the actual Sensor object that "might be not even there".
May
9
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Thank you very much for your answer! I believe the first bullet in your answer definitely describes what goes on in .NET classes, but the second one has more value (and by the way is different), because it reveals better the intended abstraction: a thing to be used vs. a thing to be described. It was hard to choose which answer to accept.
May
9
accepted What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
May
9
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
I'd say this is a killer answer, and it's not only going to help me a lot, but I believe could help a lot more people in the future. Besides, the class hierarchy example you provide maps our problem and solution domains remarkably well. Thank you very much again!
May
8
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Very interesting answer. I would ask for a quick edit: leave more explicit what is the inheritance/containment/collaboration between the four classes you mentioned. Thank you very much!
May
8
comment What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
@NathanTuggy I agree that this does not relate well with this naming convention in .NET, but regarding my current problem, I believe it is very relevant and could induce a consistent solution. I upvoted this answer, but it's being hard to choose only one to accept...
May
8
asked What's the idea behind naming classes with “Info” suffix, for example: “SomeClass” and “SomeClassInfo”?
Apr
7
awarded  Yearling