Latest Feghoots

Archived Feghoots
1 - 50
51 - 100
101 - 150
151 - 200
201 - 250
251 - 300
301 - 350
351 - 400
401 - 450
451 - 500
501 - 550
551 - 600
601 - 650
651 - 700
701 - 750
751 - 800
801 - 850
851 - 900
901 - 950
951 - 1000
1001 - 1050
1051 - 1100
1101 - 1150
1151 - 1200
1201 - 1250
1251 - 1300
1301 - 1350
1351 - 1400
1401 - 1450
1451 - 1500
1501 - 1550
1551 - 1600
1601 - 1650
1651 - 1700
1701 - 1750
1751 - 1800
1801 - 1851
1851 - 1900
1901 - 1950
1951 - 2000
2001 - 2050

Shaggy Origins

What's New

Site FAQ

Programming Problems

This computer tale was sent to us by Andy Skinner who says, "This came to me during a computer architecture course at UNC."

As fast as computers go these days, one of the strategies of a computer processor is to allow multiple operations to go on at the same time. You have to ensure that things happen in the correct order, however.

If a program instructs the computer to read from a certain memory location and then write to it, the computer must be built to ensure that the read will actually occur first, so that you don't read the value that was supposed to be written later.

There is a similar problem that can occur if you are supposed write to a memory location and then read it, but the read happens first, returning the value of the location before it was changed.

Finally, there is an error where the program was to write two different values to a memory location, but the operations happen out of order, and the memory location is left with the wrong value at the end. I think this was called a write-after-write condition, and is an example of when two writes can make a wrong.

Served by Austin Web Publishing, Inc.

Sponsored by search engine marketing firm Apogee Search, providers of world class paid search advertising management and search engine optimization services. Apogee Search is a division of internet marketing firm Leads Customers Growth.

Designed and maintained by Brian Combs (info@briancombs.net).