Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Less. (Score 1) 110

Also, the Linux version of chrome at least makes it impossible to click the middle mouse button and scroll, something that I use on a regular basis in Firefox.

I'm using Chromium to type this up in Arch on my Thinkpad, and it works fine here. Quoting a relevant bit from my xorg.conf:

Section "InputDevice"
        Identifier "Mouse0"
        Driver "evdev"
        Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"
        Option "GrabDevice" "False"
        Option "EmulateWheel" "true"
        Option "EmulateWheelButton" "2"

        Option "XAxisMapping" "6 7"
        Option "YAxisMapping" "4 5"

And it works from the X level, so it works in every application that supports scrolling (or at least, it should!). YMMV.

Comment Re:There's C then there's C written by newbies (Score 1) 407

In the case of leaking, any. You have to be a retard to leak memory in C. A free for each malloc isn't rocket science. Bad design and ignorance are the most common causes for memory leaks. You either create a mess so complicated that you can't figure where to free your memory or just don't know that you are supposed to free it. Objective-C and especially C++ have more problems because of the whole instance creation and destruction abstraction, but in the end the problem is ignorance from ex-Java people that were used to create objects and let the Garbage collector pick them up.

For complex data structures, one free for every malloc can indeed get very tricky to handle. For example, in C++, one can just write a destructor for a tree node that calls delete on it's children before delete'ing itself. Free'ing all memory is as simple as calling delete on the root node. Writing a recursive deallocator in C is trickier to get correct.

There's also issues of pointer ownership, problems that C++ and Java also inherit. Sure, this can be avoided if you have very clear cut guidelines on who owns what, but even these will fall short on some cases and those exceptions will need to be treated very carefully. The Python C interface has such guidelines.

My point is, you can be very intelligent and still manage to leak memory in C. It's completely doable, and as the complexity of your code increases, so do the chances of memory leaks. C++ and Java abstractions go a ways to help, but aren't enough by a long shot. This is why tools like valgrind are still relevant.

Comment Re:Let me present a third choice (Score 1) 270

This isn't a question of Theseus' Ship sitting in the harbour at Athens and being slowly replaced board by board until there is nothing left of the original, it's more like Theseus taking his ship out to sea for a wild party, dousing it with gasoline and burning it to the waterline, only to have Menelaus build an entirely new ship in Sparta with the name "Thezeus" on the prow two years later and then sailing it to Mycenae and selling it to Agamemnon who turns it into an amusement park where people pay large sums of money to play on half-finished rides and be beaten with sticks when they complain.

The modern day Atari is the ship that Orestes built after termites destroyed that one. And it has trouble floating because he ran out of wood before the job was done. The Mycenaean QA department insists that the boat is good and that there is no need to patch it as any sinking problems are clearly the fault of the end users.

BadAnalogyGuy... is that you?

Comment Re:That's cool and all. (Score 2, Informative) 432

Me, too, but now that Arch is splitting the [extra] repo packages, I'm wondering if I should switch to vanilla kde, since the only reason I used the KdeMod packages was because I liked my packages split. The KdeMod forums seem to suggest that the packages won't be in [kdemod-core] until the end of the week.

Well, there's a great discussion of it on the Arch forums (great before it got bogged down with bickering, although I didn't see Godwin's law being invoked).

Frankly, I think I'll move to offical [extra]/KDE tonight. KDEmod has served me great, but I think I can handle to live without all the extra patching and branding they do if it means I get 4.3 goodness a week early.

Comment Reverted Policy? (Score 1) 310

I use Bell, and I noticed the hijacking maybe a week back. Even thought of submitting a story to /.

But then it magically disappeared later on (next day?). Hasn't come back since, and before posting, i made sure that I was receiving NXDOMAIN's and not Bell's specially crafted "Domain not found" for opera: [eon@enthalpy:~]$ host Host not found: 3(NXDOMAIN) [eon@enthalpy:~]$

So, did they change their policy, or am I the only one mysteriously not affected by this?

Comment Here's an idea... (Score 1) 364

I've just recently graduated from high school, and just finished co-teaching a grade 10 computer engineering class (it's a cool program, senior students help teachers teach junior courses).

Anyways, one of the cooler cheap projects we found was building a rudimentary taser from a disposable camera. They cost about $5 (or cheaper if you buy them in bulk), and the ones we used got up to about 300 volts (good zap from that one). Sure, there are concerns of safety (one kid zapped his dad in the neck... and well, things went downhill from there), but it's an easy, quick project that let's you get involved into more interesting electronic components like capacitors and transformers (instead of the standard resistor, diode, and LED). You can even talk about how the amperage becomes minimal as 1.5 volts from a battery is stepped up to 300 volts.

Plus there's an instant cool factor to building a taser. From personal experience, the grade 10's loved it.

Slashdot Top Deals

"Open the pod bay doors, HAL." -- Dave Bowman, 2001