Darkfeign

Noctua explains it.

The noctua S12A

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

Search engine bots, or 'web crawlers' that visit the site and attempt to harvest data from it. Google, Bing, Facebook etc. In order to validly crawl the forum's data, they often authenticate themselves with forum software so they aren't assumed to be malicious.

I'm assuming you are talking about C/C++ and languages using similar implementations
of pointers.
Is a question of operator precedence. *p1[10] will first take the 11th element inthe array p1 and then dereference that, thereby selecting whatever p1[10] is pointing
to. (*p1)[10] will first dereference p1 and then select the 11th element of whatever
p1 itself is pointing to.
EDIT: Ooops, I overlooked two const in that question :o. See @WanderingFool's answerbelow. I'll leave my original answer here for posterity. /EDIT int *a is a simple pointer to an int.
int const *a is a pointer whose target location has been defined as constant and therefore
cannot be changed via dereferencing a. You can however still change a's target if you access
it via another way (see example).
Without pointers to pointers we cannot have arrays of pointers (an array's identifieris basically just a constant pointer to its first element).
Example code (I have compiled and run this on gcc):EDIT: AAARGH, the forum deleted my code when I was editing my post. I'll see if
I can recreate it. :angry:/EDIT 
If anybody spots an error please let me know.
 

#include <stdio.h>int main(){ int p1[3]; p1[0]=1; p1[1]=2; p1[2]=3; int *p2[3]; p2[0]=&p1[0]; p2[1]=&p1[1]; p2[2]=&p1[2]; /* Will print 1,1,3 */ printf("%d\n%d\n%d\n",p1[0],*p2[0],(*p2)[2]); /* These three will all print out the same number, which is the memory address of p1's first element. */ printf("%d\n",&p1[0]); printf("%d\n",p1); printf("%d\n",*p2); /* These two will print out the memory address of p2's first element */ printf("%d\n",&p2[0]); printf("%d\n",p2); int const *a=p2[0]; printf("%d\n",*a); /* Uncommenting this should throw a compilation error. */ /* a's target location cannot be changed via dereferencing a. */ /* *a=5; printf("%d\n",*a); */ /* Whereas this will work and print out 5 because we are not accessing a's target location via dereferencing a. */ *p2[0]=5; printf("%d\n",*a); return 0;}

My girlfriend was brought up a Muslim and struggles with the thought of any type of non-religious marriage. She believes that people should do what they want, and if they want to enter a civil partnership then they should be free to do so, but she also believes that marriage should be strictly reserved for a religious bond between a man and a woman, and I'm kind of inclined to agree with her.
 
Marriage is, and always has been, a religious joining of two people. Civil partnerships are a different matter.

I am a Muslim but I don't have a problem with same sex marriage. Let people do what they want.

Get yourself a solid book to learn from, as nothing beats the vast information you can constantly flick back and forth for in a text book. Something like Java: How to Program will teach you programming generics using the Java language.

The black fans aren't meant for replacements with better colour schemes, though. People don't seem to understand that they are meant for industrial applications with much higher RPMs than their regular fans.

The black fans aren't meant for replacements with better colour schemes, though. People don't seem to understand that they are meant for industrial applications with much higher RPMs than their regular fans.

Noctua NFA / P14

I uses Demciflex filters on all the intakes to my case.

If you want to become a good web developer, you need to learn things one at a time.
 
The first thing I'll tell you to do is drop PHP. At least for now. PHP, while widely used, isn't really a good language (and so isn't JavaScript). Unfortunately we have no other option than to use JS, but we can get better than PHP.
 
First, work on producing the web design. Learn XHTML and CSS. But learn proper CSS. This book is good to understand how CSS works and renders, and is also a good reference.
As for XHTML, you only need to know how and when to use the most basic tags in conjunction with CSS. Forget about tables, for example. It's all about divs. I find that whatever you'll be needing to use can be easily looked up.
 
As for actual programming, this JavaScript book is probably the best book I've read on the language.
Also, like I said, drop PHP for now. Ruby and Python, for example, are much better languages. I'd also recommend you to understand MVC, and use some framework (like Rails, or Django). But if you insist on using PHP, CodeIgniter or CakePHP are good PHP MVC frameworks.
The language documentations should be enough for you to become proficient in the language's syntax.
Finally, learn how to actually write good code. There is a plethora of material you can read on this. Usually language-specific books aren't the greatest thing. This is a general book on good programming. Code Complete, in my opinion, should be read by every developer.
 
By the way, I just realized I sent you links from Amazon UK and you're probably from the US. Sorry about that.
 
EDIT: Oh, and, most dynamic web pages need some sort of data storage. Usually databases are used, and a good (free) DBMS is MySQL. You should learn some SQL, at some point.

Welcome to the programming section. Glad to hear you're interested in getting started with some programming.
 
Like the guys above have said, there's never a right language to pick. Pick one that interests you, maybe do a bit of reading on generic programming terms, as well as the comparison between imperative and functional programming languages, and then follow other stuff like strong/weak typing. For stuff like this it can be helpful to get a proper programming book, but if you want to research online first without committing, there are a few options for you.
 
First, i'd take a look at the programmer resources thread that's pinned. This has a bunch of good resources compiled by frequenters of this section of the forum. I'd then suggest looking at a couple of the language resources there and seeing which you might prefer. Python, for example, is a great starter language as it lets you interact directly with the interpreter if you so wish, and you can avoid the need to learn specific syntax rules (another programming term you might need to look at). If you fancy getting straight into other popular languages, Java is often a popular place to start, though some people feel different about Java (C# could be your alternative).
 
C++ is often a popular language for anyone looking at serious programming, but be aware that you'll be introduced to memory management almost immediately when getting into the language. Memory management can be a pain and is avoided entirely in languages like python and java, so i'd suggest leaving it for A-levels, and picking it up after some introductory programming.
 
I started with a little PHP but quickly grew to dislike its... messiness. Python was the first proper programming language I used and it's great! Vast amount of help online, and great resources for UI and graphics etc. Then I moved onto Java. Really good for developing decent software while avoiding memory management, but there are always countless issues with Java's VM that people come to dislike it for.

I would go with the Fractal Design Define R4. I'm really surprised nobody has mentioned it yet. Weird.

If you're going the Java route then I highly recommend this book! It is very good! 

With C-style strings, you need to reallocate when changing the string. There's a more direct handling of the string. An std::string has operators for all of this already. You could make your own string class however. "rexlee_string" or something. However, that would require a lot of work from your side in optimising it. It also sounds like you're new to C++/programming, so that would be highly unrecommendable.

Here's an example:
char* mycstring = "My C-string";char* yourcstring = "Your C-string";std::cout << mycstring + yourcstring; Now, that creates a problem because mycstring and yourcstring are POINTERS. And also, it's an array, and the c-string is the pointer to the first index.
If you allocated more memory for your c-string and don't delete it before it goes out of scope, you've got yourself a memory leak.
It's much easier with std::string, as you can use the operators as with a number. (well, not - * and / etc) and it deals with all the dynamic stuff itself.

There comes a point where you need to use char arrays though. A buffer for instance. Maybe for networking or filereading/writing.
(Though, there's a C++ alternative for this too, called std::stringstream, you should look it up - it's very useful sometimes)

As for your second question, it depends.
If you want an array that only needs, let's say 10 elements, then you should go for a static array. "int myarray [10];"
However, if you're not sure how many elements you need, you should go for an std::vector.
When you're using polymorphism or have another need for pointers in the vector, use the new operator and pointers as the vector type. If you don't need a pointer, just make it an std::vector<int>, for example.

I am not a fan of iterators however. I have never ever used them to be honest. They do have a use, but it's really rare and you usually don't have to use them.
A typical loop to iterate over all elements in a vector should look like this:
unsigned int vectorsize = myvector.size();for (unsigned int i = 0; i < vectorsize; i++) { std::cout << myvector[i];} Well, honestly I never assign the size to a variable, but it's faster in some cases.

So yeah. static arrays should be normal arrays, but vectors are very good for dynamic arrays. Just the same way C++ strings are good for dynamic strings. :)

It makes everything less tedious.

Hope I was at help.

~dib

I was talking about software architecture in another thread (about organizing ideas when programming) and I remembered this book we read some chapter of in class: AOSA book (Architecture of Open Source Applications).
 
It has two volumes and every chapter of both is available at the website. In each chapter authors of an open source application talk about the architecture they used in their applications and what they learned from doing it the way they did. It is a great way to know how to structure an application based on the problems we have to solve.
 
Also noteworthy is "Distributed Systems: Concepts and Design - George Coulouris, Jean Dollimore, Tim Kindberg and Gordon Blair". It is a very useful resource for people that want to know more about distributed systems. I have used it for two courses in college and I think it talks about most of the relevant aspects in mobile computing, security, replication, consistency, etc. Here is the link to it's website (so you can see the table of contents, among other things, and not just believe my half-baked explanation!): http://www.cdk5.net/wp/

Note: Been using Windows since Win 3.11, and Linux since ~ 2005. Not a programmer by trade,
but I do use my machine to code quite a bit when I get the time (mostly C/C++, PHP, Perl at
the moment). Current main distro is Arch Linux.
 

The one main benefit I have come to love about GNU/Linux and other similar UNIX-like
operating systems is that they are inherently designed with tinkering and writing
software in mind. They are operating systems by developers for developers.
The thing that gets on my nerves the most about Windows is that while I don't
necessarily consider it to be a bad product it has so obviously been designed
with average Joe in mind that it's been dumbed down a lot and lots of choices
and options have either been removed completely or made extremely cumbersome
to achieve/set/change.
Now, that in and of itself is not necessarily a bad thing, and a completely
legitimate strategy (tbh I think it's a much more viable strategy for broad
marketing and getting computers to the masses), but it does make Windows and
its underlying philosophy less suited to my personal preferences and tastes.
The major example about this would be the extremely tight integration between
the operating system and the graphical shell (the overall Windows GUI) in Windows.
In Linux and similar operating systems the command line interface carries a much
greater importance than the GUI, and in fact you are not even required to run
a GUI.
And when you do, you have a plethora of different desktop environments and window
managers to choose from, and most of them can be quite extensively configured to
suit your individual tastes (personally, I usually prefer a tiling window manager
for work, for example).
While you do of course have the powershell in Windows, the fact that it's more
of an add-on to the GUI than the other way around clearly shows, and makes live
quite a bit more complicated for a CLI lover like myself.
Another thing which I much prefer in Linux than Windows is that configuring the O/S
and its components is much more transparent; usually it's achieved by editing pure
text files rather than ticking boxes in a dialog window. Of course, many prefer the
latter way of doing things, but personally I find it very convenient to be able to
edit a machine's configuration in a text editor on another machine and then configure
a system simply by copy-pasting a few text files onto it.
Anyway, as for programming itself, here's what I personally appreciate about coding
on Linux/UNIX-like systems:
Since the system is very configurable and those configurations are very easily portable, I can set up a machine exactly the way I like it and port that config
to other machines on which I'm doing work. This results in better work flow and
higher productivity.
The inherent design principle that the system is supposed to be easily tinkered with also adds to that flexibility.
The open source culture makes acquiring and modifying existing code, whether that be for satisfying personal curiosity or to actually achieve something
productive, easy and dependable.
In the years I've been running both Windows 7 and Linux on our household machines, I have found Linux to be more stable. I wouldn't consider Win 7
to be an unstable system (at least not for me), but I have had noticeably
more issues with it than with any of my Linux setups. Not that Linux is 100%
stable or completely free of other issues, of course. This is just a personal
observation from a very small test sample though.
Centralized software repositories with signed packages. No downloading software from different websites. It's all right there, verified and secure.
I'm sure there are others, but that's what comes to mind at the moment.  

I'd say this very much depends on what aspect of the O/S you look at. Desktop
environments and integration with other devices is definitely easier on
Windows, but from what I've used myself, that has often been more of an issue
of vendors not properly supporting Linux rather than an inherent fault of Linux
itself (getting pictures off my Canon Eos 600D is quite a bit more convenient
in Win than in Linux, and don't get me started about scanners and printers...).
Same thing with office documents. The open document standards are quite mature
at this point, the problems I've seen in my personal use have almost exclusively
been related to Microsoft's proprietary document standards not being properly
translated/converted.
But for programming, I have found Linux to be much more polished and convenient
than Windows, at least for the languages in which I've written software. And the
fact that I encounter many fewer stability issues with my Linux machines than with
their Windows counterparts makes me think much more highly of its kernel than of
the Win kernel.
Overall I do agree that there are many small niggles in Linux that still need
to be fixed. But I wouldn't call the O/S unpolished in its entirety, just certain
parts of it.
 

Indeed a very valid point. Vendor lock-in is one my my major pet-peeves when
it comes to using MS or other proprietary products. And the power of the
command line is really something I've come to appreciate.
Overall, it's maybe not so much about which O/S is inherently and objectively
superior in its entirety, but it depends a lot on your personal preferences
and what language you write software in. For somebody who's scared of the
command line, programming on Linux is probably not really something I'd
recommend, but then again, such a person maybe shouldn't be programming in the
first place. :lol:
EDIT: Ninja'd :lol:.
Spartan's opinions seem to follow a similar pattern though, I agree with his
post.

Definitely right with your main statement about Linux being entirely unpolished. It really is.

However most compilers run well under linux, I mean it's open-source like the majority of software out there now so it encourages a lot of community development and support. The terminal (bash) is really powerful and so it's great to use for interacting with a compiler that doesn't tie you into Microsoft's versions of software like C++. Most compilers are also available as a GNU port (such as GCC) so you can often get the standard implementation of your language's compiler rather than a platform-specific version like you would find with Visual C++. This makes porting code from linux to windows easier than the reverse.
 
That's my reasoning anyway. There are a lot of things I've grown to enjoy using linux for revolving around programming. The free software that supports most aspects of work is a real bonus.

Man the difference in amount of code required between C and python becomes so apparent in the above two examples.