wats jkdefrag written in?

[penguin2]

Hi
I am about to start learning programming and hope to go to a college next year (hopefully BSC). Wats Jkdefrag written in?

[jeroen]

JkDefrag was written in Microsoft Visual C++ 2005. I am not using the "++" part, it's just C.

[elfring]

I am not using the "++" part, it's just C.

It would be nice if classes and exceptions will be supported to reduce coding efforts.
Would you like to improve the software with object- and aspect-orientation?

[jeroen]

Would you like to improve the software with object- and aspect-orientation?

No, thanks. From sad experience I know that object-oriented programming will quickly make simple things extremely complex and I firmly believe programmers should stay away from OOP whenever possible. I don't know what AOSD is. I've read your link to Wikipedia and it all sounds very difficult and theoretical. JkDefrag is just a small one-man project and I get the impression that AOSD is meant for huge team software projects.

[elfring]

From sad experience I know that object-oriented programming will quickly make simple things extremely complex and I firmly believe programmers should stay away from OOP whenever possible.

I would be interested to know where you got "bitten" by this technique.

Are you going to emulate object-oriented programming always in imperative languages manually?
Do you want to stay away from inheritance?

JkDefrag is just a small one-man project and I get the impression that AOSD is meant for huge team software projects.

Aspect-oriented software development comes into play when you are looking for the automatic application of cross-cutting concerns like logging of function calls. It will become useful when you can write filters on source code where your specific reactions should be applied.

[jeroen]

I would be interested to know where you got "bitten" by this technique.

I'm sorry but I'm not interested (and have no time) to discuss that.

Are you going to emulate object-oriented programming always in imperative languages manually?
Do you want to stay away from inheritance?

I said "stay away from OOP whenever possible". I did not say "never use OOP". In certain cases OOP can be very useful, and even necessary. But it is just a programming tool and should be used with discretion. It is not a requirement, not a holy grail, and many programs do not need it whatsoever.

Aspect-oriented software development comes into play when you are looking for the automatic application of cross-cutting concerns like logging of function calls. It will become useful when you can write filters on source code where your specific reactions should be applied.

Thanks for the explanation. My feeling is that for JkDefrag all that would take far more time to implement and use than it will save.

[isgdre]

JkDefrag was written in Microsoft Visual C++ 2005. I am not using the "++" part, it's just C.

I'm with you on the over use of OO (though I do prefer it on really big projects)

Two reasons you may want flip the C++ mode on the compiler for (but still basically write C code)

Small  .LIB files for custom reusable code works great as a class.  Things like my date conversion routines.  Are all stuffed into a class.  So I don't have to worry about name conflicts and such.  Course then I just use them in my C-Styled main line code.

And Type-Safe-Linking / Function Name Mangling.   These cost you basically nothing in development time (assuming your using Ansi-C and not K&R) and can save you the occasional hair pulling event with some pretty waked out bugs.