Recent content by MikeySquid

If I help, what's in it for me?

I dunno if this has anything to do with it, but I was at the Fizzilla (Mozilla on MacOSX ) website where they claimed that there were "problems" with the g++ compiler in MacOSX. Hopefully this will get fixed.

Every one learns this somewhere along the line. There is no fundamental difference between c and c++. C++ is an enhancement to c. I'm not that knowledgeable about c so i apologize in advance for my errors. You want to output something to the screen, so you write "cout<<"Hello World";". When...

I have tried doing several of the cocoa demos form the apple web site, but I keep getting build errors: /usr/bin/ld: Warning -F: Directory name (/(path to project)/build/ProjectHeaders) does not exist. This has been driving me crazy for weeks. Any help in this matter would be greatly...

the .DStore files are put there by OSX, not Samba or sharity. You are just seeing system files which are usually hidden by the finder. Just ignore them and don't try to open or delete them.

to use sendmail as an outgoing mail server just give "localhost" as your outgoing mail server. That way mail.app will use sendmail to send mail thus. I don't know how to get it to act as an incoming mail server. This just allows me to send mail from behind a firewall. If you go to...

On OSX using g++ (gcc) you have to put an endl; after every write in order to flush the buffers. Your iostream.h is fine. you just have to do an endl. You can copy and paste the code from you book into your program, just terminate all output, whether to a file or stdio, with endl; I did some...

nothing new, no life. death. death. dying....... gone.

That did it! Thanks. And thanks to Simeon Leifer for ImageMaker - 1.1a

How do I make a disk image of my program so I can distribute it over the internet? Yes, I know I can use package maker, but disk images are cool.

hey, that's pretty darn cool. Thanks, rharder.

try >>whereis chown

That's it. Sendmail starts automatically now! thanks.

putting an endl; at the end of each cout causes a newline character to be output to the buffer and it causes the buffer to be flushed. You could do a newline character and a flush to accomplish this but just doing an endl is a lot easier.

I did some somewhat complex (500 lines of code) programs for my advanced data structures class using g++ on the command line in OSX. As long as I ended each line of code that contained a cout with an endl; everything compiled and ran fine. Without the endl... trouble. You should be able to take...