Comments for Codebloat http://www.codebloat.net Programming software technology. Sun, 26 Feb 2012 14:59:12 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Using ARP Poisoning to Create an Ad-Hoc Firewall – Part 1: The Strategy by Ståle Zerener Haugnæss http://www.codebloat.net/2011/09/using-arp-poisoning-to-create-an-ad-hoc-firewall-part-1-the-strategy/#comment-236 Ståle Zerener Haugnæss Sun, 26 Feb 2012 14:59:12 +0000 http://www.codebloat.net/?p=18#comment-236 Using iptables is definitely the only sane thing to do when doing this. The only reason why I'm not using iptables is because I wanted to write this thing from scratch, but in any real-life scenario I would definitely use iptables. :-) Using iptables is definitely the only sane thing to do when doing this. The only reason why I’m not using iptables is because I wanted to write this thing from scratch, but in any real-life scenario I would definitely use iptables. :-)

]]> Comment on Democracy and the Internet by Bruce Dietzen http://www.codebloat.net/2011/10/democracy-and-the-internet/#comment-217 Bruce Dietzen Sun, 19 Feb 2012 23:18:49 +0000 http://www.codebloat.net/?p=379#comment-217 Håkon, assuming that for the immediate future, we have to work within the confines of existing representative plutocracy, I believe that via an effective app and social media, we the people can have far more influence on elections than we now have. In short, the app would allow candidates to pledge to vote for legislation suppoted by the majority of citizens. Citizens could then view which candidates have done so and which have not. Whenever they pledge their vote for a candidate, their pledge is shared on facebook and google plus. Most incumbent Federal representatives will likely refuse to take these pledges, but the "not yet corrupted" candidates should jump on it. A simple polling app like this is just the start. If you are interested in discussing this further let me know. Regards...Bruce Håkon, assuming that for the immediate future, we have to work within the confines of existing representative plutocracy, I believe that via an effective app and social media, we the people can have far more influence on elections than we now have. In short, the app would allow candidates to pledge to vote for legislation suppoted by the majority of citizens. Citizens could then view which candidates have done so and which have not. Whenever they pledge their vote for a candidate, their pledge is shared on facebook and google plus. Most incumbent Federal representatives will likely refuse to take these pledges, but the “not yet corrupted” candidates should jump on it. A simple polling app like this is just the start. If you are interested in discussing this further let me know. Regards…Bruce

]]> Comment on Using ARP Poisoning to Create an Ad-Hoc Firewall – Part 1: The Strategy by John Hanson http://www.codebloat.net/2011/09/using-arp-poisoning-to-create-an-ad-hoc-firewall-part-1-the-strategy/#comment-209 John Hanson Sat, 18 Feb 2012 07:57:05 +0000 http://www.codebloat.net/?p=18#comment-209 I am thinking about doing this same thing but with a machine loaded with snort and the proper iptables rules to make an IPS using arp spoofing I am thinking about doing this same thing but with a machine loaded with snort and the proper iptables rules to make an IPS using arp spoofing

]]> Comment on While or For? A Comment On Code Entropy by Antonio Pérez http://www.codebloat.net/2011/10/while-or-for-a-comment-on-code-entropy/#comment-25 Antonio Pérez Sun, 16 Oct 2011 09:45:22 +0000 http://www.codebloat.net/?p=302#comment-25 I'm not into using C++0x for production code yet, so I only use <code>std::for_each</code> for very simple operations. When I have to do some more complex things inside the loop, I have sometimes tried out creating a local functor and use <code>std::for_each</code>, but the approach is not so clear, since the functor has to be defined before the loop: <code> std::vector v; struct Operations { void operator()(int i) { // Actual operations } } std::for_each(v.begin(), v.end(), Operations()); </code> Given that I use this kind of loops when the operations to be performed in each iteration are more than a couple of statements, and that I try to keep my methods short, the surrounding scope of the loop is quite small in most cases. So I would sacrifice the good practice of not leaking variables into surrounding scope for the sake of readability. I’m not into using C++0x for production code yet, so I only use std::for_each for very simple operations. When I have to do some more complex things inside the loop, I have sometimes tried out creating a local functor and use std::for_each, but the approach is not so clear, since the functor has to be defined before the loop:


std::vector v;

struct Operations
{
void operator()(int i)
{
// Actual operations
}
}
std::for_each(v.begin(), v.end(), Operations());

Given that I use this kind of loops when the operations to be performed in each iteration are more than a couple of statements, and that I try to keep my methods short, the surrounding scope of the loop is quite small in most cases. So I would sacrifice the good practice of not leaking variables into surrounding scope for the sake of readability.

]]> Comment on While or For? A Comment On Code Entropy by Lars Storjord http://www.codebloat.net/2011/10/while-or-for-a-comment-on-code-entropy/#comment-24 Lars Storjord Tue, 11 Oct 2011 09:30:39 +0000 http://www.codebloat.net/?p=302#comment-24 For standard containers in C++, I'd prefer using <code>std::for_each</code> and lambdas, assuming C++0x is an option. Of the two snippets shown in your post, the <code>while</code> is definitely more readable. An interesting question in this case is whether readability or good practice (not leaking variables into surrounding scope) should take priority. What do you think? For standard containers in C++, I’d prefer using std::for_each and lambdas, assuming C++0x is an option. Of the two snippets shown in your post, the while is definitely more readable. An interesting question in this case is whether readability or good practice (not leaking variables into surrounding scope) should take priority. What do you think?

]]>