sorted by: recent | see : popular

Content Tagged with technology + languages

Very nice quickly learn how to use .htaccess

If the source object has a longer lifetime than the listener, and the listener doesn't need the events anymore when there are no other references to it, using normal .NET events causes a memory leak: the source object holds listener objects in memory that should be garbage collected. There are lots of different approaches to this problem. This article will explain some of them and discuss their advantages and disadvantages. I have sorted the approaches in two categories: first, we will assume that the event source is an existing class with a normal C# event; after that, we will allow modifying the event source to allow different approaches.

I have been asked a few times in different circumstances why I feel the need to create my own language instead of just working with Io. That is a very valid question, so I’m going to try to answer it here. First of all, I like Io a lot. Ioke is close enough to Io that it will be obvious who the parent is. In my mind at least, the differences are in many ways cosmetic and in those that are not it’s because I have some fairly specific things in mind.

In this conversation Microsoft Technical Fellow and Chief Architect of C# Anders Hejlsberg sits down with programming language design legend and computer scientist Guy Steele (creator of Scheme and expert in several languages ranging from LISP to Java).

In this video Anders Hejlsberg takes a look at the future of programming languages and sees the trends; declarative, dynamic and concurrent. As the chief designer of the C# programming language and a key participant in the development of the .NET Framework Anders Hejlsberg has a lot to say about this development - not just as a wish but also as something that can be realized.

So I’ve done about two weeks of real work in Haskell. Here are some observations.

A tutorial to create a newsletter application for your website. It allows users to subscribe and unsubscribe from the newsletter. A simple online administration interface (an ASP.NET page) allows the admin to create and send newsletters/emails.

It is obvious that we live in interesting times for programming languages. But are they interesting enough? What are the current trends in cutting edge programming languages?

The birth of object-oriented programming is often traced back to Simula 67, which was released in -- you guessed it -- 1967. However, I recently encountered an example that goes back even further. That example is in the Data Control Block (DCB) that was an integral part of the user interface to IBM's mainframe operating system, OS/360, that I believe first saw the light of day in 1964. I haven't kept in touch with that system's successors, but I would be surprised if a similar data structure does not still exist today.

One of the authors of the Fan programming language (http://www.fandev.org) talks about his experience at the JVM Summit.

I needed a List with fast random access capabilities. Standard implementations of a List takes O(i) to access the ith element. I am using Scala and arrays do not really cut as a well-behaved functional data structure. Besides I needed dynamic resizing, persistence and good worst case complexity. Anyway I was trying to justify implementing Okasaki's Purely Functional Random Access Lists ..

A few days back, Robert Virding released a stable version of LFE - Lisp Flavored Erlang, a concurrent Lisp based on the features and limitations of the Erlang VM. Unlike Lisp it doesn't have global data or mutating operations. Instead it has the goodness of Lisp macros, sexprs, code-as-data together with the Erlang power of pattern matching and binary comprehensions. And the best part is that LFE hosts seamlessly with vanilla Erlang/OTP.

I am becoming increasingly frustrated by Common Lisp's age. On the one hand, history makes it what it is: Mature, well-documented, thoroughly understood and practical. On the other, it fails to keep up with current system designs, lacking convenient native support for rich data structures, infrastructure access and parallel programming. No programming language choice is without tradeoffs and in that respect, and I'll still chose Common Lisp in many situations. Realistically, though, Common Lisp cannot be the only language in my tool chest. For browser work, Javascript is much more practical, and for parallel programming, I'm on the lookout.

Different programming languages have different takes on how to handle I/O. The basic way is to wrap the kernel syscalls, here's the basic open() call in assembler:

Ioke is a strongly typed, extremely dynamic, prototype based object oriented language. It’s homoiconic and got built in support for several kinds of macros. The languages that most closely influence Ioke is Io, Smalltalk, Self, Ruby and Lisp (Specifically Common Lisp).

There must be a name for that particular form of programming masochism which involves wringing the maximum effect out of the minimum of code. If not, someone should invent one!

I spent last week at the JVM Language Summit, a small conference focused on non-Java JVM-based languages. It was populated almost solely by either JVM implementors or bytecodes-are-my-new-assembler types.