I don't think I can learn C....

[Karlos]

whabang wrote:
AARGH! By all gods and somewhat  important deities! :-o :-o  :-o

I was planning to learn C or C++, but this is too much!
/me runs back home to give a big hug to FreePascal :-D

Fear not, for 'tis merely an exmple of confusication - with a capital C :-)

No real program would look like this. Unless part of the Win32 kernel :-D

[whabang]

/me sure hopes that you are right :nervous:

[Karlos]

Have no fear matey,

C (and C++) is actually one of the most logically laid out languages there is. It's stuctured, terse and flexible. It has very few keywords, all the basic operators you could ever need and everything else is done using functions.

Before anybody starts - the above is true, once you get use to it :-)

I'm gonna be unemployed real soon so that long awaited tutorial site I was considering (see here) may see the light of day :-D

[Crumpster]

@ Karlos

Cheers for the update, have read through the backlog now.

How come your losing your job? (I take it you work in Software Development??)

Cheers,

Crumpy

[Crumpster]

Incidentally, I would be interested in that tutorial site.
Can't remember if I piped up before.
I know a tad of C++  (a really ickle bit) so would welcome such a site.

[Karlos]

Crumpster wrote:
How come your losing your job? (I take it you work in Software Development??)

Too much time on amiga.org :-D. Nah, sigh of the times :-(

[Piru]

Piru wrote:
68000, AmigaOS (SAS/C 6.58):
mystery 1048 ----rwed Today

Anybody beaten this yet?

These with my half-working 68k gcc 2.95.2 setup:

mystery-68000-gcc                  968 ----rwed Today     16:41:16
mystery-68020-gcc                  928 ----rwed Today     16:40:14
2 files - 1896 bytes used

...I wonder if I missed something with SAS/C though, it should gererate smaller code imo.

[Karlos]

Wow, that's pretty titchy!

I guess the 020 code benefits from some addressing optimisations...

[Atheist]

I wonder how big the .exe file would be on win32 vs. 68K vs. 68020 (or higher) vs. PPC if it was just one big

printf("On the first day of Christmas my true love gave to me/n
a partridge in a pear tree./n/n
On the second day of Christmas my true love gave to me/n
two turtle dovesin a pear tree./n/n
On the third day of Christmas my true love gave to me/n.......")

I think I got the printf(" ") part right.

I ask because, on win(lose)dohs, if you go to the trouble of writing IMPRESSIVE code, it still bites you in the end.

It is VERY IMPRESSIVE code to me, at any rate.

AmigaOne! Things are gonna get REAL interesting!!!

[iamaboringperson]

im not sure what that code was... but it reminds me of some code i saw in a magazine once that decoded some kind of DIVX or DVD encoding, that was said to be unbreakable!

ROFL! unbreakable they said...
HAHAH! completly secure they said...

[N7VQM]

Atheist wrote:

I ask because, on win(lose)dohs, if you go to the trouble of writing IMPRESSIVE code, it still bites you in the end.

One doesn't always get bitten.  

For example, my portion of my senior project was a Win32 program to control WinAmp.  The user interacts with WinAmp thru a touchscreen LCD connected to a serial port via an RF link.  I found similar projects to control WinAmp thru a game port.  The smallest of those I found had a 300KB executable file and all the really did was allow you to send the basic commands like play, stop and FF/RR.  My program gives you control over those plus will send the name of the track playing, navigate playlists (with names) and had rudimentary support for manipulating WinAmp's equalizer.  

Based on the size of the other programs I found, I thought mine would be in the neighborhood of 500KB.  Imagine my and my partners surprize when the final executable was only 28KB.

[N7VQM]

iamaboringperson wrote:
im not sure what that code was... but it reminds me of some code i saw in a magazine once that decoded some kind of DIVX or DVD encoding, that was said to be unbreakable!

You're probably thinking about CSS and DeCSS.  I find it amusing that you can buy a t-shirt with DeCSS in PERL silkscreened on it.  I am a circumvention device....

[Agafaster]

All for a good cause, too - top of the Group !

anyway, we are here to talk about one of me other favourite topics - C.

I had a go tidying up (ie: reformatting in an attempt to make more readable) the 1st program.
I came across summat I hadnt seen before there, and in Piru's program too - the use of a Comma. what does this signify ?
In particular for Piru's program in the 2nd for loop:

[color=000000]putchar(--l%80?i:10)[/color][color=00ccoo],[/color]o=D=l%80*.05-2[color=00ccoo],[/color]i=31

I presume it means many statements per line or something... :-?

[Karlos]

It's a sequencing operator - not many C programmers even realise this, using it only to seperate declarations of variables etc.

For example

x = (f(), g());

AFAIR, the value of x is whatever g() returns, but f() is always called before g().

This seems pointless when you could write

f();
x = g();

but it does have it's uses :-)

[Casper]

It's a sequencing operator - not many C programmers even realise this, using it only to seperate declarations of variables etc.

It's one of those things the longhaired geeks that sit in the basement all day coding wanted in C so they can write code no one else understands and feel very super-leet.  :-)

[Karlos]

Hey dude, I got my hair cut 2 years ago. My avatar image just old, that's all :-D

Actually, for C code, the comma operator is often useful in function-like macros that are supposed to 'return' a result and need to do several operations without ending the statement (ie with a semicolon).

A lot less useful in C++ where you just have an inline function.