Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×

Comment: Re:Bring on the lausuits (Score 1) 599

by vilanye (#49177927) Attached to: Republicans Back Down, FCC To Enforce Net Neutrality Rules

The only time the "people" win is when the Federal Government does not regulate. Regulation is strangulation and, ultimately, death.

Yeah, it was awesome when there were no labor laws, no safety rules, no controls on pollution.

Look how much damage the banks caused after deregulation of banks started in the 80's and compare that to the 4 decades previous.

Corporations need to be leashed at all times and beaten regularily.

Comment: Re:Bring on the lausuits (Score 1) 599

by vilanye (#49177861) Attached to: Republicans Back Down, FCC To Enforce Net Neutrality Rules

There is no GOP candidate that can get the support of the lunatics currently in charge of that party that could win a general election.

Someone like Huntsman could win the presidency but the nutbags that control the GOP would never nominate him because he is reasonable and intelligent. Two attributes that are no longer welcome in the GOP.

Huntsman would likely have beaten Obama in 2012.

The GOP will have to jettison its extremists if it wants the white house.

Comment: Re:Such potential (Score 1) 520

by vilanye (#49074315) Attached to: Nim Programming Language Gaining Traction

Enforcing whitespace in the language weakens it.

Add in the sad decision to not make everything an expression in Python and you have a weaker language with zero benefit to go along with the enforced whitespace.

Guido is almost as stupid Rasmus.

Python used to not have any scoping at all which is why you have all those redundant self self self self self....

Comment: Re:It was a terrible example of went to use a goto (Score 1) 677

by vilanye (#49074161) Attached to: Empirical Study On How C Devs Use Goto In Practice Says "Not Harmful"

> I say "please don't use goto" and instead have a "cleanup_lock" function
> and add that before all the return statements.. It should not be a
> burden. Yes, it's asking the developer to work a little harder, but the
> end result is better code.

No, it is gross and it bloats the kernel. It inlines a bunch of junk
for N error paths, as opposed to having the exit code once at the end.
Cache footprint is key and you just killed it.

Nor is it easier to read.

As a final argument, it does not let us cleanly do the usual stack-esque
wind and unwind, i.e.

        do A
        if (error)
                goto out_a;
        do B
        if (error)
                goto out_b;
        do C
        if (error)
                goto out_c;
        goto out;
        out_c:
        undo C
        out_b:
        undo B:
        out_a:
        undo A
        out:
        return ret;

Now stop this.

        Robert Love

http://koblents.com/Ches/Links...

Science is to computer science as hydrodynamics is to plumbing.

Working...