KnowledgeTree for C#

-
Knowledgebase update 3 -- C# branch added to knowledgebase

C# Knowledge Tree


Copyright ©Rajesh Patkar, All rights reserved.

Comments

Post a Comment

Popular posts from this blog

MelodyCrypt -- Harikavach ( level 5 )

-
Image
New to Harikavach >> Harikavach Introduction The Challange The challange in Harikavach is that it is a  HandCryption   technique. This implies that it must be humanly possible to encode/encrypt the message and decode/decrypt the message, without using a computer and in a reasonable time with minimal effort. Computers can be used to compromise the message. Computers can use Brute force technique to break the code. In Brute force technique the computer can try all the possible keys ( or a highly probable set ) on the message to compromise it. With increasing computing power, it is easy for a computer to try millions of key combinations within a reasonable period of time. This is the problem with level 4 . There are fixed number of keys that can be generated using Scramble Clock .  Let us consider that we place all the possible keys in a Set. Then this set is the Key Set ( Key Space ). The Key Set is finite for Scramble Clock and also finite for Harikavac...
Read more

Why Java Objects only on Heap?

-
Image
B ackground Last month I had asked a Java related question to all my students on a facebook post . Why is it that in Java, Objects are always to be allocated on heap? Why is dynamic allocation the only option in the toolbox of a Java developer while creating objects? It was a very interesting discussion on facebook. Many participants, my students and otherwise gave good arguments in defense of the Java Language Design. One of the arguments that came out shining, was that of the possibility of unsafe allocations on Stack Frame. Special thanks to Ted Lum, Chetan Parmar, Nishant Verma, Vaibhav Desai, Tusharkumar Thomar, Vimal Sakhiya, Clair Roma Henry, Subham Gadi, Makarand Bhosle, Prasad Kowli and Nirav Kothari   for their participation and valuable arguments. Let me now, put forward my perception on why Java Language Designers would have taken such a decision. The following content in this article assumes that the reader is aware of memory models and lif...
Read more