Larian Studios Forums General Chat Favorite Quotes

"merchandising!"
- yogurt

It is mostly true with code demonstrated by the younger generations, it just looks as reckless as their favourite music and clothes fashion.

I was brought up under Royal British Discipline, cut nails, combed hair straight morning lines etcetera.
This was reflected in my code too and my code professors use it in their text that came after.
I never give but meaningful variable names.
I always comment my code.
I never add useless features.
I always have a clear target to achieve.
I never drink before driving my keyboard. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

I've should of known ASCII stupid question, get a stupid ANSI !"

On your marks Faile, on your marks. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

You asked for it Morbo, no .... you pleaded in fact. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

dec25 = oct31
ofcours.
i never heard of using the octal system.
soo it's probably the ansestor of the hex system?

aa does me remember the good old days at university, digital techniques.
DEC25=OCT31
or
(25)10 = (31)8
2*10^1 + 5*10^0 = 3*8^2 +1*8^0
20+5 = 24+1
25=25

<img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" /> <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" /> <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

Dear Student Bean.
Error correction list:-
One mistake corrected.
2*10^1 + 5*10^0 = 3*8^1 +1*8^0

Good luck.

<img src="/ubbthreads/images/graemlins/wave.gif" alt="" />

must been a typo <img src="/ubbthreads/images/graemlins/confused.gif" alt="" />
thinks for a minute <img src="/ubbthreads/images/graemlins/think.gif" alt="" />
<img src="/ubbthreads/images/graemlins/badsmile2.gif" alt="" /> -> definately a typo

(and walks innocent away out of the class room )

That�s more like it, I am sure Bean.
Save the mistakes for partial derivatives in advanced calculus. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

<img src="/ubbthreads/images/graemlins/evilgrin1.gif" alt="" /> <img src="/ubbthreads/images/graemlins/evilgrin1.gif" alt="" /> <img src="/ubbthreads/images/graemlins/evilgrin1.gif" alt="" />

aah.. you've got to love mathematics <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />

it's unbeleivable that almost everything can be put into a mathematical calculation.

Indeed.

<img src="/ubbthreads/images/graemlins/wave.gif" alt="" />

Ahh... too bad the censoring spoils the rhyme!

Five points! <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />


In a group project at Uni, one of the coders did comment his code. Mind you, with his choice of language, we'd really rather he hadn't. Further more, the on-screen display was titled "Information Kiosk Bulls***". He does realise we're getting marked on this, doesn't he?

Haaaaaaaaahahahah....he he he hilarious. <img src="/ubbthreads/images/graemlins/delight.gif" alt="" /> <img src="/ubbthreads/images/graemlins/delight.gif" alt="" />
Still LOL.
No, no I must control myself and stop laughing, really.

Ok.
It all begins with discipline and ends with discipline.
A coder should never comment his code for himself but for others, because that is the original reason for commenting, maintenance.
A code may be abandoned for many months before revisited and then re-comprehending it would depend greatly on verbosity, good spelling and a perfect choice of names representing input process and output data.
An integer counter may be called �i� but what is so wrong about calling it i_Finished_Pencil_Counter?
Why should lpL_Molten_Core_Temperature be called T1?
The better we choose the names, the less the needed comment, because such names are self explanatory.
In conditional loop-sections we need to comment the purpose of the loop and its conditional exiting information.
Comments should be as short and specific as possible to avoid confusion.

Of course �Nocando� titles are a big no no. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />
It only reflects the mentality of the programmer and in that case, I assure you that he was completely a misplaced person who belongs to a brothel. <img src="/ubbthreads/images/graemlins/evilgrin1.gif" alt="" />

Are you refereeing to:
Girls = Evil
Boys = Evil ^3

<img src="/ubbthreads/images/graemlins/question.gif" alt="" />

<img src="/ubbthreads/images/graemlins/evilgrin1.gif" alt="" />

I agree, although if you use a lot of long named variables, it can make code difficult to read because the maths and methods get lost amongst the variable names. I also have the habit of reusing variables to save space (in the vast amounts of available memory - yeah, I'm a a fool), so using detailed names can actually cause confusion. Anyway, I'm starting to ramble off topic here.


I would agree that a trip to the brothel would probably get rid of some of their built up frustration! Hackerz really need to get out and get someone. It'll at least give them something else to do.

Anyway, quotes... Nope. I'm drawing a blank. <img src="/ubbthreads/images/graemlins/disagree.gif" alt="" />

Indeed, but I was not giving out all my secrets here.
There is also the secret of acronyms aliasing and variable overloading.
This allows you to declare a legend at the top of the code that does not consume memory at run time but makes variables clearer on meaning and at the same time allows the usage of the very short forms (4 letters at most) in equations to shorten them and clarify the logistics.
I have the habit of multiplying by 2 through barrel shifting rather than multiplication to squeeze execution time by the nanosecond, so do not worry about anything being wasted here.

As for the quote:

I'll have to remember those tips, DAD. Thanks! Now, what's the barrel shift opperator in QBasic...?

Top line response = You are welcome. <img src="/ubbthreads/images/graemlins/smile.gif" alt="" />
Bottom line response = I cannot remember.

I must have used Quick Basic a couple of times, but when the majority was using it I was mainly using assembly, ANSI C and Advanced FORTRAN. Now my serious work is in VC++ and my fast burner is VB.
Hence, I have practically skipped QB and TB although Borland did a fantastic job IIRC.
You would not believe the fantastic graphics we produced in DOS 640 x 480 256 colours in the old days.
If you are aware of TOPAZ then you might have an idea of the quality. It was Amiga 1000 that kicked in and computers were never the same again after. The first virus was born on an Amiga by the way and it was a joke inspired by the fantastic speed of the graphics engine. The programmer wanted his joke to be sticky and persistent because it was a frightening screen and a mad laugh, so he wished to be scarier. The idea to embed code to make a copy in memory for being triggered later on periodically came from that concept. Viruses evolved since then to carry several destructive missions in retaliation from pirates who bypass the security codes. The earliest internet communications helped the spread of that concept from the Amiga and onto Mackintosh of apple computers and from there to Intel-MS PCs.

At that time Bill Gates was drinking wine from bottles not from barrels. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />
Only those who took the RISC were drunk from barrels that could shift binary numbers left and right. <img src="/ubbthreads/images/graemlins/biggrin.gif" alt="" />
Most probably QB never had such an operator.
Kindest regards.


<img src="/ubbthreads/images/graemlins/cool.gif" alt="" />

It was a joke! <img src="/ubbthreads/images/graemlins/tongue.gif" alt="" />