sorted by: recent | see : popular

Content Tagged with languages + .NET

PowerShell provides the += operator to add one hash table to another hash table. By default this operation will result in an error, if both hash tables have at least one key that is common in both collections. In some cases you may want to have a more granular control. For example, you don't want to get an error, if not only the key, but also the value is common in both collections. On top of this somebody might want to allow an overwrite, if the key and the value are going to be identical as result of the merge. This could be useful, if the hash table is used as template for replacing strings. Updating the master table by adding a key value pair that refers to the same string would mean to exclude this particular replacement pair from the replacement transactions.

Many people object to the suggestion that multiple return statements in a single method can help simplify code. Where did the idea come from? Is it still valid?

Every now and then I need to investigate bugs that get exposed because countable "things" are less or more than expected. In my special case I was dealing with an application that manages subscription handles to memory registers of programmable logic controllers (PLC). These programs are called Data Access Servers. Occasionally we get calls form customers reporting that the number of handles is less, or sometimes more than expected. The first step to debug this situation is to find out, which handles are missing or which ones are duplicates. This blog post describes how PowerShell's Compare-Object cmdlet makes this task, which used to be a pain in the "peep" now a piece of cake.

We're getting closer to the next major release of F#: our first CTP release out of Developer Division. As a result, now is a good time for me to start talking about some of what I've been working on for the past few months: the F# project system. Over the coming weeks I'll describe some of the new-to-F# project system features we'll deliver in the CTP, providing a "sneak peek" at what's coming.

There has been a lot of talk in the last year or two about Java losing ground to newer languages and about which language is going to replace Java as the dominant language going into the next decade. After all the smoke clears, what should the reasonable person conclude? Is it time to move on?

When learning a new programming language it isn’t enough to know the syntax, you must also take the time to learn the idioms and styles for the language. Unfortunately those idioms and styles develop over years and F# still hasn’t had its ‘official v1'.0’ release. So where do we start?

Use the power of linq Create a form with some controls on it and a textbox called textbox1. then but this in the load event of the form

Why is the introduction of Erlang style message passing into F# interesting? Well you may have never heard of Erlang but if you’ve ever used a cell phone you’ve probably used an Erlang system. Erlang was originally built by Ericsson and released as open source in 1998, it was built to support the highly distributed and fault-tolerant systems required to support mobile phone networks. Many people consider Erlang to be the language that gets concurrency right.

One of the areas we found was with how we cache data. We cache results fully scored and ranked, which is fine. The problem lies in how we were populating the cache. It's something we would never notice in development, because when you're just firing up the debugger, you aren't running multiple threads against that code.

I just came across a language that I never heard of before: Fan. [code snippet] After a few hours surveying the language, I have to say that Fan seems to get a lot of things right.

This is a collection of SQL hacks, right now we there are 8 sections and between 70 and 80 hacks.

The question is: "Will Polyglotism and DSLs make Java the Last Big Language?" While I think the post is interesting, it's a funny question to ask. Even today I use a minimum of 3 languages: Java, SQL and JavaScript. Then one could argue that perhaps XHTML and CSS each has a place among "languages". If you're working with any RIA technology, you're most likely to encounter ActionScript. If you're a committed Java fan, you might see some JavaFX Script in the future... that is if Sun's tragic branding skills don't kill before it's released (first Java, then JavaScript, then JavaFX Script? WTF). Anyway, check out the article... :-) [Nitpick: I would argue that C# would be "The Last Big Language", as it was introduced 7 years after Java. It's arguably as "big", at least in terms of trying to be everything to everyone and having libraries available for everything from medical imaging to star mapping.]

The second development chunk focuses on creating documents to index, and munging them into a format to hand off to an external library. There are examples of calling a .NET library from F#, mutable values, function composition, and several other spiffy sounding things.

This tutorial walks you through how to take screen-shots in C#, using visual studio. Very simple and includes a Visual Studio solution for those who might want to look at how a screen-shot function can be implemented into an application.

I was in Amanda Laucher's F# talk yesterday and I asked about whether F# was able to tell if a function was pure or semi-pure. (A pure function is simply a function with no side effects, and a semi-pure function is one that only modifies locals) I was just a bit curious if F# was able to tell if there were any immutable variables that had been introduced into method, or if any mutable variables had been changed during a method. Well, I got my answer and then I made a statement that I probably definitely should have shut my mouth on. I essentially asked if introducing mutable variables would cause the F# compiler to not do its tail recursion optimization.

We take a critical look at who people are assuming will use F# and who is actually putting their money where their mouth is when it comes to this exciting new technology. The results are surprising!