Any coders here?

[Redwoood]

It's getting late. I'm tired. It's Saturday night and I'm sitting in front of my computer.
G%^ #$mn project that is due next week and doesn't seem to have an end.
My headache doesn't help, either.

Ok, just wanted to share my feelings

Let's see if I can at least get that crap to compile and link...

 

[beowulf]

Ahahaha, I see you haven't been getting enough sleep. What are you coding and with what?

 

[Redwoood]

That's a research project I'm working on.
A C++ implementation of a cryptographic protocol.

I'm down to 18 compiler errors. <sigh>
I think I'm gonna go to bed. Not gonna start to write a copy constructor now...

You should go to sleep yourself, it must be 6 am where you are.

 

[jaskin]

Quote:

Originally posted by Redwoood It's getting late. I'm tired. It's Saturday night and I'm sitting in front of my computer. G%^ #$mn project that is due next week and doesn't seem to have an end. My headache doesn't help, either. Ok, just wanted to share my feelings Let's see if I can at least get that crap to compile and link...

LOL! Java stuff? A friend of mine is in UWaterloo too seems to me he does lotsa coding there.

 

[dhwilkin]

As a fellow coder, I feel your pain, man. Funny thing about coding: You might get 38 compile errors, fix two of them, and on the next compile get, say, 47 errors!

Do you have to use C++? Go for Java and forget about the stupid copy constructors! And most memory leaks...

 

[Redwoood]

Actually, I like C++.
I like it better than java (I don't wanna start a programming languages war though)

Just sometimes... a don't like it quite as much

Well, time for a shower and 6 hours of sleep.

 

[pearle]

Java programmer here. Used to program in C/C++.

I've been toying with Smalltalk and Python of late

- pearle

 

[aos]

You're getting **errors**? Consider yourself lucky. Reminds me of time (1991) when I worked on a Viterby decoder and spent a full week tracking down error that would case variables to assume unpredictable values after any kind of read from a file... Very hard program to debug since there was lots of abstract concepts and plenty of high dimension arrays etc., so you have to analyze it in detail at every step, you get the idea. And then you find out you've forgot to include stdio.h but compiler didn't complain and just assumed all undefined function arguments to be int-egers...

 

[lini]

pearle: If you like Smalltalk, then maybe you should have a look at Squeak (www.squeak.org) - highly recommended by a friend of mine (Mike Rutenberg, if you happen to know him...).

Greetings from Munich!

Manfred / lini

 

[dhwilkin]

Quote:

pearle said... I've been toying with Smalltalk and Python of late

Never used Python... but Smalltalk, blech! I really don't like Smalltalk!

Quite possibly the only language I dislike more is Lisp... welcome to the land of parentheses...

 

[pearle]

lini: hehe, Squeak is what I used to introduce myself to Smalltalk

I'm just trying to expose myself to different language environments. It can't hurt!

- pearle

 

[Redwoood]

Hey, did I mention that Pyhton rocks?

Perfect for quick prototyping, good for anything else.
It's just sometimes that you need C++ for some 'real' work


Bye

Redwoood

 

[ai0tron]

I heard that coding in assembly is the best way to write software. Is that true?? This guy online claims that coding in C++ produces bloated software.

 

[thomas]

I think that although assembly is definately the fastest and most efficient method of programming, i don't think it is practical to use it for complex programs. The comands are just too basic to do complex tasks. C++ is already very fast, and it allows you to do complex tasks with much less work, and keeps everything well organized...

but what do i know, all OAC computers teaches is "pascal", haven't looked at C++ for more than 5 years,

btw, redwood, how's waterloo, is it mainly hard to get into, or is it also very difficult once you're inside....

 

[dhwilkin]

Assembly? Well, if you know what you're doing, then yes you can write very fast code. Or you could just skip assembly and write machine code, even faster! But the main reason nobody writes big servers and whatnot in assembly is that it would take forever. By the time you're product came out, you'd be several years too late. Not to mention, assembly code is platform-dependent. And I don't even want to think about the nightmare that would be debugging a server written entirely in assembly...

Oh, and C++ compilers CAN produce bloated code, but not always. Besides, most of the times you write the majority of your code in a high-level language like C++, then code the parts that absolutely must go blazing fast in assembler.