Mail Archives: djgpp/1998/08/04/17:30:50
Destination: Merlin <merlin__ AT geocities DOT com>
From: Gruber Gerhard
Group: comp.os.msdos.djgpp
Date: Mon, 03 Aug 1998 22:18:13 GMT:
>i have never used fprint.. only c++'s cout. And i do know how that works..At least i think...
>The point is that i haven't stopped trying to figure out how it works or how any other
>function, allegro, libc or otherwise... I mean don't you wonder sometimes how they work...
>when i wonder how they work i go find out.
I do the same, but that's different from saying that one HAS to learn it in
order to use it. I'm absolutely not interested in sound cards programming. But
I still like it if I can produce some sounds without having to know what
registers I have to manipulate. On C64 I took sounds out of games and made
them run stand alone. But I still don't know, and also don't care to, how to
program one by myself. What's wrong with that?
>Yes.. everyone does use shortcuts to varying degrees but I PERSONALLY think this is no excuse
>to stop learning. I don't care what you learn or what programming language you use. I don't
Continues learning doesn't mean that everybody should learn what yo seem to
think best or important. You can learn a lot of things when you use a library.
You simply learn other things that you would miss because you try to figure
out the libraries internals.
>to learn, I am just stating that i don't like to use allegro becuase it makes me feel like i'm
>not doing it myself. Then i asked for other people's OPINION. I did not accuse or call people
You don't have to use it. But what about libc? or any other lib that you
surely bind to your program'? Or do you program your entire startup code and
library functionality by yourself? If so, how compatible and portable are this
programs? My guess is, zero. There are reasons why to do something yourself
and other reasons not to do it yourself. My primary goal is that all my
programs run under X and Windows. So writing all that stuff for myself would
means that I not only have to learn Windows/DOS, I'd also have to learn every
machine detail of all machines I'd like my stuff to run. On the other hand, a
good library works on all systems as expected, hiding the details.
>> Ho and believe me, the people playing my games dont give a flying
>> monkeys what language i use or how much i know :)
>
>I do. When i play a game i often wonder what language it was coded in and how they did some
>thing's they did do.
Then you should start learning to read the assembly code in order to determine
on which compiler the program was produced. That is possible, because I know
some compileres when I see their code. When do you start learning? :)
--
Bye,
Gerhard
email: sparhawk AT eunet DOT at
g DOT gruber AT sis DOT co DOT at
Spelling corrections are appreciated.
- Raw text -