ml01172

I agree with the previous post. It is indeed a bit complicated system that one has to get deeply involved with if planning to use all its capacities. Of course, if you plan only surfing and listening music on it - it's not so hard to learn. You will get rid of all kinds of spyware, worms, viruses etc. and you'll have a smooth surf with no worries. But if you plan on doing more than that, you'll have to learn a bit about it.I'm using Slackware, but in the past I used SuSE, RedHat, even Fedora, a little bit of KUbuntu, and I must say it's all about the same thing with little differences. It's more or less irrelevant which one you choose, but I'd recommend not choosing Slack since it's a little tricky when installing new programs, configuring drivers, updating software etc.

It is not important whether it's Pascal, C or any other language at the first year of studies, as long as it's 1. procedural (to make it easy to learn starter algorithms) 2. Simple in terms of libraries and environment (so the learner doesn't get confused with all the GUI API, huge IDE's etc.)We at our university in Belgrade (Serbia) at the first year studied Pascal (for half a year) and C (other half). I find it very useful since when we were taught C++ it was quite easier than if we didn't know C already, and then came Java which was a piece of cake once we knew C++, etc.Therefore I don't agree C is going to become "obsolete" ever, especially that it's still the fastest of all higher languages, that it is a father of almost 90% most popular languages today (C#, C++, Java, Javascript, PHP, etc.) which all use C syntax.It is also the main language for developing Linux (it is a question whether they're ever going to switch to another language), Unix, and a majority of popular games today.

Actually, the situation is a little bit more complicated than that. cout << doesn't serve the purpose of "outputting text into that black box", but something more than that. Each and every application has three default files open: standard input, standard output and standard output for errors, known as STDIN, STDOUT and STDERR. They DO NOT represent "black boxes", "screen" etc. They actually represent abstract data channels that can be redirected anywhere - to the screen, to a file, to a device, over the internet etc. It is only that DEFAULT redirection is to the output of the shell that ran the application. Looking back to visual programming, one might redirect standard output to an object that displays messages graphically, so in that situation cout << "something" would be displayed at the screen in any graphical manner developer wants.

You guys realize that half of those attributes are obsolete in HTML? If you try w3 validator, it will tell you the same thing.For an example, <... align="center">, <center>, <font color="...">...</font> etc. (everything related to exact "look" or "style" described in HTML) is obsolete and should NOT be used. CSS should be used instead.HTML in general is used only to describe document structure, not the document appearance. So, instead of <center> you should use style="text-align: center", instead of <font> one should use style="color: red; font-family: sans-serif", instead of BOLD, ITALIC, UNDERLINE (<b>, <i>, <u>) corresponding CSS variants should be used.Also, <em> should be used to define the given text as EMphasized, not only the style itself.

GD library isn't related to any of the user-libraries and scripts, like coppermine gallery etc., but strictly to PHP. You have to install or upgrade your PHP at the server so it contains GD. Try doing this, for an example. Download PHP source from PHP.NET (try getting the version you already have installed) and, if you're on Linux, do the following: 1. Unpack the PHP package you got 2. Change directory into the created PHP directory. 3. Type: ./configure --with-gd 4. If configuration successfull, type: make (not "make install", and not necessarily as root) Once compilation process is over, look into the "modules" directory. A library with .so extension should be there so just copy it into your local "modules" directory for PHP (usually /usr/lib/php/modules or similar). Restart your web server. Cheers

It would be great if you added some info on debugging programs with threads. I'll take your turn now Typing: info threads will result in displaying which threads exist in the moment. The numbers in the first column (1, 2 etc.) represent the threads' ids. Once you know these ids, you can switch to corresponding threads like this: thread 2 GDB will now be executing that thread in the front, while other threads will continue working in the background. You can use the usual techniques described above (next, quit, step, continue etc.) in this thread. Debugging with threads tends to be complicated since multiple things happen at the same time. One might consider using sleep() in a thread so it doesn't "run away" before you switch to it in the debugger.