Welcome to RCF - WHF

Nightrider · Sep 25, 2004

Trigger driven means that when an assignment is made to a variable, it triggers an event that launches elsewhere. The triggers are generally removed from the source where it was triggered, so it can be difficult to follow, especially if you can't easily distinguish the triggers from normal code. And one trigger could act like a domino affect triggering other triggers all completely removed from the code that originally started it. That is quite different from Function driven code. You can actually see the call to the function at the source, so it is much easier to follow...

Your friend may be new to this but he writes very complicated code, which isn't always a bad thing unless many others have to be able to follow it too...

munky2

Chris Powell · Mar 31, 2007

Aah right I think I've got it.

Nightrider · Sep 25, 2004

I once was told to work on code that wasn't working. I was able to convert over 700 lines of code into 3. It was incredibly complicated to follow my code but it did work correctly. I had to write about 700 lines of comments to describe what I was doing just in case someone else had to work on it later...

So complicated code isn't always bad, but it can be a real PITA for others who have to work on it...

Shocked

Chris Powell · Mar 31, 2007

I guess Karlos didn't expect anyone else to work with the code though, which could be the reason why the codings not commented out Sad

Nightrider · Sep 25, 2004

That's probably true. I once had a boss that told me to comment everything even if no one else will ever see the code. My comments actually helped me to figure out what I was doing when I looked at the code later on after not seeing it for a long time. So good coding practices are that you should always comment your code no matter what. I'm sure that Karlos will discover that as he gains more experience...

munky2

Chris Powell · Mar 31, 2007

no doubt

Nightrider · Sep 25, 2004