vmathew

4 ms·

1. 1.▲
   by vmathew 15y ago

   It has FExpressions, the earliest form of macros. The arguments of an FEXPR is evaluated on demand. ( http://nostoc.stanford.edu/jeff/llisp/19.html )
2. 2.▲
   #35 device review(youtube.com)

   2 points by vmathew 16y ago|0 comments
3. 3.▲
   by vmathew 16y ago

   In the first place, a language that exposes pointers may not be able to do away with null. But as for languages like Java, the problem can be solved with the help of an implicit, non-mutable default object: Foo foo; // initialized to
4. 4.▲
   by vmathew 16y ago

   class Node { // May not be a real situation for a Node class, // but makes a point. Node getLeft() { return left; } } // No more checks against NULL. In fact code becomes simpler f
5. 5.▲
   by vmathew 16y ago

   This is one possible way of doing it: class Node { static const Node EMPTY_NODE = Node(); String key; String value; Node left = EMPTY_NODE; Node right = EMPTY_NODE; Node(String key, Str
6. 6.▲
   by vmathew 16y ago

   A systems programming language that expose pointers will not be able to shed NULL. But a higher-level language can and a "pure" OOP language should - because null make objects unable to respond to messages. Something that claims to belong t
7. 7.▲
   Do we really need null?(home.vmathew.in)

   5 points by vmathew 16y ago|10 comments