The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
What you mean is: some designers prefer you don't use tables. And this has lead to designers using everything but a table to do things that, really, should be done using a table.
For us: yes, we have tables for layout where we shouldn't. We're actually in the midst of planning updates to this. However, there are cases where tables actually provide layout safety because a table can reign in bad HTML. If you allow user generated HTML (like these forums) then you need a mechanism to ensure the HTML they provide doesn't break things. HTML and CSS filtering works (mostly) but there will always be cracks. Sandboxing (sort of) this HTML inside a table has proved (for us) to be a neat safety feature for wayward HTML.
* Pointers are bad, everything must be an object;
* Managing memory is bad, everything must be garbage collected;
* Native is bad, everything must be interprteted or JIT-compiled;
* Performance doesn't matter, computer power is illimited;
* Tables cannot be used for layout.
From one web developer to another, I agree. Tables should only be used for showing tabular data, not layout. However, keep in mind CP has been around a long time, way before CCS3 or even CSS2 became popular. People used to use tables for layouts before CSS2. These days it's discouraged (rightfully so), but the creator of CP (Chris Maunder) has been around since dinosaurs roamed. And you can't always just up and change a website that serves millions of people so quickly.
That being said, for any new development you're doing, definitely do not use tables for layouts... just tabular data.
My old funny uncle is having a sound sleep meters away. He was snorting so loud I couldn't focus on anything. I screamed "You old man can't play that bass a little less louder?". And now he's snorting less loudly. I don't know how people respond in sleep automatically and keep going. lol His snort sounds so controlled and careful now.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
1. No programming questions in the Lounge.
2. Where's the programming question in your post? "Remember x?" hardly qualifies as a "programming question".
3. So, to answer your subject, no.
4. You have proven your point though.
The guy who wrote the software I'm currently trying to fix had a neat fuzzy logic system going.
As far as I can decipher from his "code", it went something like this:
NULL - Was I really meant to initialise it?
TRUE - Well, it seemed as good a value as any other so I just went with it.
FALSE - See true.
TRUE OR FALSE - I really haven't a clue what's going on and maybe calling it IsNotInCollection added to the confusion so I'll test for both true and false because one of them's bound to be right. I think.
TUESDAY AFTERNOON - Something always has to be different on a Tuesday afternoon, doesn't it?
POSSIBLY - Might be, might not be, better not test just in case.
WOMBLES - I wasn't really thinking about the requirements when I wrote this bit.
CATFISH - Catfish? Catfish are cool, m'kay. They've got those weird probe-like things that look a bit like whiskers. That's why they call them catfish, you know. They can get really, really big and stuff. What's this software meant to be doing again?
WIBBLE - I'm going to show off now and try to do some LINQ. I'm good at LINQ and I'll be even better when I've learned it.
OOPSIE - Damn! I almost got it right, I was just binding to a completely unrelated value. It happens.