Lopatir wrote: The article you read was written by someone that either referred to a different programming language, or doesn't understand the C/C++ language definitions; char* is not a type in C/C++. Far as I can recall it was a columnist in the C++ Programmers Journal. I suspect that they did in fact have a passing familiarity with the language. And since at least two columnists in that magazine participated in the C++ ANSI committee I suspect that their opinion on that subject of C++ would have carried more weight than any other random developer. They provided a rational for why that form was more appropriate which, far as I can recall, was not grounded solely in the semantics in the language but more in common usage of type specifiers. But I could certainly be mistaken about what they actually said. Not to mention of course "The Annotated C++ Reference Manual" written by Ellis and Stroustrup which in section 4.7 has the following code examples. void f(char* cptr, void* vptr) ... int* p1 = ... char* cptr; int* iptr; void* vptr; So seems like the creator of the language prefers that form as well. My original usage was grounded in the form you are championing but that was based on K&R. I found the article I read persuasive enough that I started using the other form.

CListCtrl Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt

I've grown quite fond of JUCE which is pretty much a library that covers most aspects you'd need. And cross platform, of course.

.jpg wrote: I have a 3 years old daughter, and now a new born baby, from the past 3 years I have over 1 TB of photos and video...f I am going to keep those growing size of photos and videos until they are 18 years old, that would be a lot of money. You do realize of course that a rough estimate of your final storage is 12 TB? That is ((1TB/3years)*18year)*2). So if you handle the storage yourself via hardware you would need 24 TB. This of course presumes that there are no more children nor grand children. Also keep in mind that cloud based services are businesses - not absolutes. They can and have ceased business without warning.

:doh: 6 not 7! I made that mistake too many times when I was at Uni... :sigh: And I had forgotten the auto comment feature as well. Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water

Both cant create jpeg file without filename... are you sure you are windows user ? :-D

I find using my Windows 7 desktop at work frustratingly slow and difficult compared to my Linux desktop at home (we've had an MS-free house for about five years now). And I also love my Linux^H^H^H^H^H Android phone. The inability to do trivial things like delete files because they're in use and the general sluggishness of the desktop drive me spare in Windows. On the other hand, the lousy video drivers and often poor-quality userspace [gconf and bonobo, I'm looking at you...] wind me up with a GNU system (be it Linux or BSD). And mono... ugh.... But, given a choice and without any specific task requirements that force Windows, I'll take Linux anytime thanks. One interesting thing though is that we were recently burgled and my wife's laptop was stolen. While we're waiting for the insurance, she's been using a similar spec. Windows laptop borrowed from work - and has been complaining about the frustrations of having to use Windows. Although reasonably clued up about computers in general, she's not a "techy" and doesn't go near the CLI without instructions. -- What's a signature?

.jpg wrote: Are there any cool ways to name your project? I think it is quite "cool" to name projects with names that describe the project. As a professional developer and someone that knows that between 50% and 90% of the total cost of any application originates from maintenance and not the initial development I attempt to produce code that will be easy to maintain. And I certainly think that descriptive names are more likely to achieve that than fun ones are.

ahhh nokia, Nokia's audience is not what they want it to be, in my opinion that is. Personally I love Nokias sturdy reliable not filled with gadgets that I don't ever use or any of our providers can provide. as to why Nokia is going down, is because I believe they are focusing on sturdiness and reliability rather than innovation and system overhaul which is usually extremely risky. to my opinion that is

That's my experience too. I have a Qt application for Windows, Linux and MacOS. Windows makes 98% of the business, MacOs 2%, Linux 0%. The interesting part is that this doesn't reflect the download statistic of the demo version. There is roughly 10% for Linux and less than 2% for MacOs, but virtually nobody buys the Linux version. With that attitude, Linux will never become a mature platform. I'm about to cancel the Linux version. It's only the ease of cross-compiling a Qt project for Linux that makes me releasing to Linux binaries.

Or the keyboards. Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.” I wouldn't let CG touch my Abacus! When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.

A TCP packet is not likely to contain only one character of data. A URL is quite small enough, ordinarily, to fit within a single packet, and it would be very strange and inefficient to split it up into single-character chunks. I also think you might be confusing different layers of the network stack. IIS doesn't know anything about packets or acking. That happens at the TCP layer and below. IIS merely sees the request as an ordered data stream from which it reads until hitting the sequence of characters indicating the end of the request, and then responds to that request. It may well close the TCP connection if it keeps reading and reading and the request turns out to be too long, or send a response and then close the connection even sooner if the URL portion of the request is too long (a total request could be very long if a POST is involved), but there isn't some kind of byte-by-byte acceptance response from IIS to the browser. Typically IIS doesn't even send anything at all (although the underlying TCP mechanisms are sending packets in both directions) until the whole request is complete.

Because it is the only social network in which you can "friend" dead actresses. I've lately been inundated with friend suggestions like Helen Hayes, Brett Somers, Gale Sondergaard, Nancy Culp, etc. Odd, that. Never give aversion therapy to a masochist. The results are unpredictable. My Mu[sic] My Films My Windows Programs, etc.

AdamNThompson wrote: I would like it if you would elaborate though on how you go about measuring productivity, and why you feel that number 2 on my list is not measurable. Some ways that have been tried for absolute productivity. - Bug count/lines of code - lines of code - Bug origination (integration, system, production) None of them are very good and all have problems. They are however all objective. Myself I doubt delivery time is viable as it is often dependent on other things. Additionally it isn't a matter of when but rather how accurate the schedule was in the first place. That last is a measurement that can be made and one that can improve over time but that is a process specific to project/task management and not code development. In terms of "maintainable" you woud first need to provide a definition that leads to measurable stats. For example is your code more maintainable because it takes you less time to deliver the next release? Or someone else? And do the requirements of the next release have nothing to do with the release time? What about the time between release updates - would you expect an app that was written in 2000 and is only now being updated to be comparable to another that was released in March (2011) and will have the second release in June? AdamNThompson wrote: I feel like I can look at code and tell if it's going to me maintainable. I look for things like meaningful abstraction, IOC, layered architecture, and so on. If someone is making database calls in a code behind file in their UI project, or is cut and pasting the same block of code throughout their work (both of which I have seen done before), I would consider that suboptimal to maintain, and therefor unproductive. I can look at a plate of food and guess whether I am going to enjoy it a lot, a little or not at all. And whether I could cook it myself and even make it better. That however has nothing to do with whether there is anyway to measure, in concrete business terms, how 'good' the food is nor if my attempt will be 'better'.

Unfortunately, it has everything to do with your answer and code. Even though the OP is obviously new to C/C++, it doesn't hurt to learn good practices right from the start. At any rate, it wasn't a suggestion: it's me saying that it is bad practice to use pointers and string literals in that way, for the reasons I explained. This is quite independent of the programmer's intentions. So my point is: your solution was almost correct, except for that you should use 'const char*' everywhere to work with it like this. This could potentially save the OP lots of time trying to debug weird access violation errors later on, as the compiler will be able to inform you when you are doing something inappropriate that you are allowed to do when just defining it as 'char*'. Now if you think I am entirely wrong and that it is in fact not poor practice, then I'd love to hear your arguments.

As I am now, only the CLAW persists... ((λ (x) `(,x ',x)) '(λ (x) `(,x ',x)))

What do you mean by "it does not work"?... The code as written just does not compile for a simple reason: Your second call to PrintBy does not match the signature of the called function. You either declare a second overload for PrintBy taking a proper pointer-to-method of Printer or (much better) you rely on standard library abilities: #include #include template < typename TPrinter > void PrintBy( std::string const & pString, TPrinter pPrinter ) { pPrinter(pString); } // Your stuff ... int main() { ::PrintBy( "hi", Print ); ::Printer p; ::PrintBy( "hi again", std::bind( &::Printer::Print, &p, std::placeholders::\_1 ) ); }

Yep. utf8-cpp

keep having kids until your wife's boobs touch the floor. ;) -- ** You don't hire a handyman to build a house, you hire a carpenter. ** Jack of all trades and master of none.

In Soviet Russia the cross-platform makes the project.