Cccommunicate news letter is out.
[
When you share personal data with a friend on Facebook you also share it with the Facebook apps your friend uses. Read that again.
That’s right. When the price is free regard yourself as the product.
This news letter is found online here.
This news letter is sponsored by Pain, Jump and Imagination.
This news letter doesn’t come with a ridiculously long eula.
]
Installing Windows8 consumer preview on a Max/OSX running Parallells works like a charm. I even saw a button in Parallells to install Win8; I guess Parallells downloads and installs everything. I had downloaded the gigs already so I chose to install from ISO.
It can also be an advantage to install on a mac since the touchpad is fantastic.
Next mission is to install Visualstudio11.
Update:
Visualstudio11 works.
Update:
Multitouch on the Mac mouse does not work when you write your own WPF applications as mentioned on Stackoverflow.
Cccommunicate news letter is out.
I have created a better Windows keyboard layout for developers. It is very similar to the US keyboard but with a few tweaks that makes it nicer to work with. For a regular US keyboard user the only difference is less pressing of the shift key.
Download it here, of course as open source.
Longer story:
The US keyboard is a good working start for a better developer keyboard since most languages are created for the US layout.
Symbols often need shift to be pressed.
As developers we often press ( and ) and = and @ and the other symbols at the top row, but to reach them we need to press shift. That is a total waste. So I switched them. With Keyboard 1337 you instead press shift to reach the figures. Or use the num pad.
Alt-gr-\
Swedish developers have a problem with the keyboard layout. For instance backslash “\” is reached through “alt-gr”, a button to the right of the space bar and then 7. There is no good way to press those two buttons without hand gymnastics. My solution is to switch to US layout.
ÅÄÖ
I need ÅÄÖ and instead of switching keyboard every time I need one of those letters I put them in their regular place but activated with alt-gr. A solution that works better than it sounds.
Physics
The physical keyboard layout doesn’t change due to installing a new keyboard layout so you have to have a bit of fantasy or switch the plastic keys if possible.
I have started at a new job and after some days of contemplation and a try-out I decided to go for running Windows as a virtual machine under OSX on an Macbook pro.
I had several reasons in no particular order.
– The hardware is nice. The rumour is that Apple don’t buy cheap stuff on the spot market. When you use a Mac it feels nice and I can play with it in the store; ordering a Dell over internet doesn’t give me the chance to handle it.
– I need to learn other stuff than the Microsoft stack. If you use a thing for long enough you start to believe the world has to be that way. I want to get that rust out of my fingers. I have installed linux several times but without being forced to use it, it has all but collected dust. Digital dust.
– I want to get started with using virtual machines for developing. I have tried developing on a Windows virtual machine on a Windows host before but failed; it was too easy to use the host for everything.
17″ screen, 7200rpm hd, antiglare. The rest is stock and will be upgraded as time goes.
I intend to use Parallels for running my Win machines virtual. If the hardware can’t handle it I should be able to use the same virtual drive through Bootcamp.
I can’t afford SSD right now even though it was a requirement to start with. Apple’s prices are too high so I will buy on the spot market later.
I can’t afford 8gigs right now and Apple’s prices are too high so I will buy on the spot market later. I am running Win8 on 1,5gigs and that is not enough it needs at least 4. My machine doesn’t take more than 8 gigs according to the specs so I’ll probably have problems running more than 1 virtual OS at once.
I have played with the first Mac thousands of years ago, worked with Mac during the 90s and I have played with my SO’s Macbookpro so I know a little from beforehand. But playing and working with pre-OSX is not the same as knowing.
The win keyboard is arguably better than the mac one. It has page up and page down as separate buttons. Yes it can be remedied by pressing fn at the mac keyboard but that not the same. The delete button is also missing and corresponding work around is more cumbersome, instead of 3 delete presses for deleting 3 characters one has to press 3 shift-right and then one backspace. If you are used to fiddling around with the mouse for moving your caret 3 characters to the right this isn’t a problem for you. But then you probably have blunt knives in the kitchen anyway.
The OSX keyboard doesn’t have a properties button but I instead have to use shift-f10 in Windows (which really is what the properties button is a shortcut for). It. Is. Not. A. Proper. Workaround.
The apple touch pad is awesome. It is awesome enough, on its own, to argue for running Win on a Mac through Bootcamp. The best touchpad I have tried on Win isn’t even close to the Mac. I use 10.7.3 and it has an even more awesome touchpad with up to 4 (5?) fingers recognition for doing stuff. I gladly confess it isn’t perfect and sometimes miss my swipes but it won’t push it from 1st, 2nd and 3rd place.
I recommend turning on all the features on the touchpad. They features are not turned on out of the box.
On the other hand, keyboard handling and shortcuts in Windows is way better than in OSX. OSX is created for people with three hands, two on the keyboard and one on the mouse. If you think using the mouse for moving around in your application is state of the art you probably have blunt knives in the kitchen too.
Give me the Mac touchpad and the Windows keyboard handling and we have nerdvana. Wait… that is what I am sitting with right now!
Appstore is a must. But why does it want to know so much about me? On my Android phone I can download anything free without giving away my credit card number.
Through my bank I can create virtual credit cards with a limited amount of money on. It works on Appstore.
OSX doesn’t have as many good gratis text editors as Windows has.
The installation of OSX is smooth. Start the machine, do your choices and you are good to go. Windows, on the contrary, requires a day and a half for reboots and checks for updates. Add another day if you want Visual studio and Sqlserver.
OSX doesn’t run the full fledged dotnet framework but Mono. Dotnet is a good framework so it is a shame.
I use Keepass on Mono in OSX. To make a long story short it fails in several ways. The most noticeable is that the good copy-password functionality in Keepass doesn’t work. Add mismatched highlighted text, crashes and that it sometimes refuses to start. It might be a bad port of Keepass, it might be shortcomings in Mono. If you give me time I will investigate but as for now I am short of spare time.
OSX has a proper *nix/BSD terminal. Windows still has its console and Console2. Windows also has Powershell which is *nix terminal piping made right. Like so: in *nix one can do lots of automation from the terminal through piping and griping. A big drawback is that what is piped is the text output and not the contents. Powershell can also pipe data between apps but uses real dotnet objects instead. Ponder this for a while and realise what a leap that is in functionality and updatability.
One of the reasons for choosing to use both OSX and Windows is to not fall into the belief that everything should look like Windows. The start menu is one of them. I have always thought the start menu was a good idea, especially after Vista when one could start entering text directly and let Windows find the application or document for you; much like Spotlight in OSX. Now I have seen OSX’s 5 finger pinch which gives me all apps as icons over the whole screen. (think iPhone) It has the same drawback as the Iphone app chooser – there are lots of icons but no system to separate them for making them easier to find.
Minimising and maximizing works better in Windows than in OSX. There are system wide short cuts and visual clues (menus that pop up). OSX can minimize a window but one needs the mouse to open it again. Sometimes.
Which brings me to Safari which has recently passed IE as the least good web browser. Example: if you detach a tab you cannot attach it again. Unless you choose to mouse to the menu window-merge all windows. When every tab in every Safari window is put into the same window. I am not saying all other browser behave differently but right now I am irritated on Safari so it has to wear my flames.
I am not irritated on Evernote but it is equally mousey. If one hides a window of Evernote one has to use the mouse to get it back.
The TextEdit editor in OSX is better than Notepad in Windows. On the other hand Notepad is (easily) replaced with other good and gratis editors. Good and gratis editors in OSX are not as plenty.
I miss the light telling me the HD is working. When the machines doesn’t respond for a few seconds it is a good clue to what is going on – is it the HD or the code that is the culprit?
My OSX version has switched up and down while scrolling. I say the OSX direction is the correct one.
Here is why: when I programmed scroll bars back in last century I learned that there is no correct way regarding what is up and down. The document goes down when the scroll bar goes up when the earlier/above text is shown when the up arrow is pressed. Now we have learned to use fingers for moving documents around and now there is only one way to look at it; the correct way.
You, dear reader, might disagree, but I suggest you embrace change, mr Quixote.
Parallels has its own Swedish keyboard. I don’t know the difference between that and the regular OSX one.
Windows ctrl-alt-del is in Parallels fn-ctrl-alt-backspace.
I have yet to figure out where backslash is on my Swedish OSX, Swedish Win and English Win keyboards. I am not sure Parallels work properly there.
Folders in Finder is opened through command-o. Enter does something else. I won’t say it is 100% bad but I believe the Windows choice of making Enter open the folder is better.
I really miss having standardised command-o for opening, -w for closing a window, -h for hiding a window, and command-comma for settings in Windows. Alt-f4 and ctrl-f4 are steady standards in Windows but the combinations were probably invented by a chiropractor gone mad. Ctrl-o is standard and alt-enter almost so. OSX could learn something from Win what happens when a window is hidden, opening a hidden window on OSX changes from app to app and often requires the mouse.
Switching tab in windows is ctrl-tab and command-left/right in OSX. Unless where it is ctrl-tab. The gratis editor Textwrangler has its own scheme where switching document isn’t visualised as a table and requires the mouse. Which made med ditch Textwrangler since a text editor is keyboard centric and shouldn’t force me to stretch of for the mouse or move my fingers to the touch pad.
Ctrl-left/right is used in Windows for selecting a word. In OSX it is used for switching desktop. I had to turn that functionality off in OSX. I now have to do a 4 finger swipe to change desktop. I see no immediate other solution.
When I get in to heavy programming in Windows on this machine I will bring forward my Windows keyboard. I wonder how my muscular memory will react when it is subjected to the OSX layout. I plan to update this article. Let’s see if I remember.
Pressing the function buttons in OSX requires the fn key. In Windows it does not. Thankfully there is a setting in OSX System preferences to turn this off. Recommended if you run Windows under OSX.
Zooming in OSX is done through ctrl-scroll up/down (two finger swipe) much like in Visual studio. Windows has a similar functionality I can’t recall the name of and shortcut for. I have a feeling the Windows variant works better.
Update
Multi monitor support does work. Sometimes. The first time I chose it (can’t remember the name and can’t get to it – more on that further down) my second monitor lit up directly; just like “extend monitor” in Windows. A Windows boot later it refused to extend to the second monitor. Until it worked again. Unfortunately I don’t remember what I did because later Windows stopped recognising the second monitor again. Some googlingwithbing later I found a new button in Parallels that makes my second monitor availabla again. It is even better since it puts my monitors on the Mac desktops so I can choose where to se a single win monitor and single mac monitor at the same time in my multi monitor setup. According to my historical statistics this too will fail soon and I will find another solution/button/checkbox/reboot.
Here’s a caveat with my “new” multiple monitors in mac/parallels/win: I can’t get to the Parallels menu in Windows. Therefore I can’t see the original menu I used for multiple monitors and I can’t do any other settings either.
Is the text above unreadable? Yes it is. Understanding multiple monitor setup in Mac/Parallels/Windows is undoable so it is just right the explanation is unreadable too.
Cccommunicate news letter is out.
Which List/Collection to use and where?
What do I choose and what do I have to choose from?
I have found no comprehensive, and good, list so here is a stab at it. Much of it thanks to Gary Short and his video.
Update: There is more, and deeper, information by James Micael Hare.
Update: With Dotnet3 came ReadOnlyObservableCollection. I have not looked into this one.
Update: With Dotnet4.5 three new read only lists are found; IReadOnlyList, IReadOnlyDictionary and IReadOnlyCollection. There is also the Immutable namespace that contains the whole set of basic list variants like Dictionary, List, Queue, Set, Stack, Array, Dictionary, HashSet, SortedDictionary and SortedSet.
Update: At the time of writing we are at Dotnet4.7 and even more lists might have been added. If you know of a such, please comment and I will update this list.
Also: Many of the list types I have annotated “Dotnet 4.5”. This does not mean the type ends with Dotnet4.5 but that I have not investigated the type’s existence later than 4.5.
Update: Now we are at Dotnet 4.8 and have been told it is the last one since Dotnet Core and Dotnet Standard has happened; not to mention UWP and Xamarin. Then there is Mono (non Xamarin variant). I have stopped updating versions as they got stale so fast.
Update: It is now Dotnet 7 and I have lost count of all the list-ish types. There is also the parallelised version of list-ish. Nick Chapsas has 13 fast paced minutes about performance on List<>. Tip: the size of the list affects which is fastest and parallel has effect and Span too, albeit with side effect.
http://msdn.microsoft.com/en-us/library/6sh2ey19.aspx
Dotnet 2-4.5
( This chapter has the most information and explanations that won’t be repeated in for the lesser used lists. )
This is the one we “normally” use. If you use it as return you should use IList<T> instead as interfaces gives you more decoupling.
Good: Simple to use. No brainer, especially for short lists. Usable with lambda.
Bad: Adding can be expensive. Removing even more so. (I haven’t checked Insert but it should be expensive too.)
There are some caveats with List<T> though.
One is that it allocates space in chunks that increas as the list grows bigger. By your first myList.Add(…) dotnet allocates 4 items. When you add a fifth element it doubles the allocation so 4 new are allocated. Now 8 items are allocated, 5 used and 3 wasted. When you add your 9th, 8 new are allocated.
Like this.
4, 8, 16, 32, 64, … you get the idea of doubling.
Now note that the doubling not only is a waste in space but also ticks. Every time the list is extended a call to Array.Copy(…) is made and memory copying is expensive. I haven’t any good figures but check the Gary Short’s cast linked in this article and wind to 15:30.
When one allocates directly in the constructor like this:
var myList = new List<int>(){1,2,3,4,5};
nothing really changes. Behind the scenes 5 myList.Add(…) are called and you still have 8 items allocated.
A way to mitigate this is to tell the compiler how big list you want:
var myList = new List<int>(5);
Now you get 5 items, allocated once. On the other hand it also changes the allocation scheme to multiples of 5
5, 10, 15, 20, …
which might be exactly what you wanted or not.
The way to do this at constructor time is:
var myList = new List<int>(5){1,2,3,4,5};
If you know you are adding a lot of items avoid looping and instead use .AddRange like this:
myList.AddRange( new int[]{6,7,8,9} );
Remove does a linear search for your object. Performance is O(n). RemoveAt just goes to the index and removes the item which gives us O(1). Unless you have veeery long lists both methods are considered fast. But. Remember that Remove(…) does a comparision which comes in three flavours IEquatable<T>, Equals and bitwise. Wind to 18:00 in the linked cast.
Sorting is done with Quicksort. Unless you have special cases like an almost ordered list or – even worse – an ordered list, this is a fast sorting algorithm. Performance is O(n log n) in best case and O( n^2) in worst case.
If you have an ordered list, which we often have, you could get some benefit of randomising the list first. Or the obvious: check if the list is ordered before sorting it. Or use another list or collection; which this article is about…
http://msdn.microsoft.com/en-us/library/he2s3bh7.aspx
Dotnet 2-4.5
This is a double linked list.
Good: Fast for Add, Remove and Insert.
Bad: Searching is slower.
Since Add, Remove and Insert only manipulates the item at hand and the items just before and after the performance is O(1).
Searching and going to a certain index means traversing the list and hence performance is O(n).
http://msdn.microsoft.com/en-us/library/xfhwa508.aspx
Dotnet 2-4.7
Good: Fast for searching. Implementing your own key type can be a problem.
Bad: Only one key.
The dictionary is a key-value store. This is considered fast since the comparision between two items depend on a key and not on the whole item.
Here the caveat is on the comparision on the key. The comparision is dependant on the hash key which, if expensive, makes this list less performant.
A simple key like a string (not too long) or a number is fast when the key is evenly distributed. What this means is that lots of keys around 100 and a few around 10000 makes worse performance than if the keys are spread 100, 200, 300, 400 etc. Not a tool good example of me and that is why web searching is your friend.
There is a helper method for quickly creating a dictionary from a GroupBy. See here for example.
Caveat: if you have an object as the key comparision is done through IEquatable.Equals or by overriding Equals and when you do (which you should do once in a while just for the fun of it) you have to override GetHashCode too. And following this you must now grokk both hashing of an object and the hashing theories. Personal recommendation: don’t write the code in a few minutes just because you can; invest a couple of hours in it. It will pay off in the long run.
Also note that hashes are only theoretically unique. This means you can get two hits for the same hash.
Then note that if you write a class where Equals is not overriden dotnet will compare the reference; but if you have an anonymous class dotnet will do a shallow(?) comparison.
http://msdn.microsoft.com/en-us/library/bb460184.aspx
Dotnet 3.5-4.6
Good: has several items for each key. Fast searching through the key.
Bad: has several items for each key.
This is a Dictionary<TKey,TValue> variant with the addition that it can take several items for the same key.
Note: For a reason unkown to man the interface is totally different though; it uses an extension method ToLookup which takes lambda as parameters. I guess there is some good rationale behind this since it the guys behind this are smart.
One creates a Lookup<TKey,TValue> by calling ToLookup on an IEnumerable<T> and the syntax is quite nice.
Note that this list is immutable so nothing can be added to or deleted from the Lookup when it is created.
http://msdn.microsoft.com/en-us/library/ms132319.aspx
Dotnet 2-4.5
There is a generic SortedList too.
Good: Sorted. Fast retrieval [O( log n )].
Uses less memory than SortedDictionary<T>.
If you add lots of data at once, use SortedList<T> instead of SortedSet<T> or SortedDictionary<T>.
http://msdn.microsoft.com/en-us/library/dd412070.aspx
Dotnet 4-4.5
Good: Sorted. Fast retrieval [O( log n )].
See more at http://msdn.microsoft.com/en-us/vstudio/ee906600
http://msdn.microsoft.com/en-us/library/f7fta44c.aspx
Dotnet 2-4.5
There is a generic version too.
Good: Sorted. Fast retrieval [O( log n )]. Faster insert and remove than SortedList<T>.
http://msdn.microsoft.com/en-us/library/dd381779.aspx
Dotnet4-4.5
Used for concurrency. They don’t solve the problem of concurrency conflicts but mitigates them. Every fetch of add should be tried. The add method is called TryAdd and return true/false depending on if you succeeded or not; the same with TryTake. Yes, this means an if(…) for every such call and corresponding handling. That is one of the reasons concurrency is hard. And fun.
Check out int.TryParse for an easier-to-test method with the same functionality.
http://msdn.microsoft.com/en-us/library/dd381779.aspx
Dotnet 4-4.5
Used for concurrency. They don’t solve the problem of concurrency conflicts but mitigates them. Every fetch of add should be tried. The add method is called TryAdd and return true/false depending on if you succeeded or not. Yes, this means an if(…) for every such call and corresponding handling. That is one of the reasons concurrency is hard. And fun.
http://msdn.microsoft.com/en-us/library/dd267265.aspx
Dotnet 4-4.5
See ConcurrentDictionary.
http://msdn.microsoft.com/en-us/library/dd267331.aspx
Dotnet 4-4.5
See ConcurrentDictionary.
http://msdn.microsoft.com/en-us/library/dd394988.aspx
Dotnet 4-4.5
See ConcurrentDictionary.
Represents a particular manner of splitting an orderable data source into multiple partitions. Not only does it work particular but is also is named totally different. I predict this list will almost never be used since noone finds it.
http://msdn.microsoft.com/en-us/library/dd267312.aspx
Dotnet 4-4.5
See ConcurrentDictionary.
Now this collection is slightly different regarding add/remove since it can block and give you true safety. But also deadlocks. If you don’t know what a deadlock is, and don’t fieel like studying this, just go and ask a SQL guy for transactions and deadlocks and he’ll have about the same problem and answers. If you understand what s/he says you’ll understand BlockingCollection.Add too.
One can set a timeout. Ask the SQL guy if you wonder what that sentence meant.
http://msdn.microsoft.com/en-us/library/ms668604.aspx
Dotnet 3-4.5
Used typically for MVVM in WPF or Silverlight.
Good: can tell others about its state changes.
If you have a collection and want to watch over it to see if it changes – then this collection is for you. Start a WPF project if you want to play around and test it.
Due to a reason known to only a few this collection is defined in the WindowsBase assembly.
Uses List<T> internally so anything that applies to List<T> applies to ObservableCollection too.
http://msdn.microsoft.com/en-us/library/system.collections.specialized.listdictionary.aspx
Dotnet 1.1-4.5
A Dictionary implementing IDictionary as a key-value pair linked list. Check Dictionary for what that means.
This list is suitable for lists with fewer than 10 items and even though you probably can retrieve the items in the same order every time, don’t depend on it since Microsoft has specified that the order might change.
It is generic which means type casting is up to you.
http://msdn.microsoft.com/en-us/library/system.collections.specialized.ordereddictionary.aspx
Dotnet 2-4.5
Uses key-value pairs and have them ordered. Duh.
It is generic which means type casting is up to you.
http://msdn.microsoft.com/en-us/library/system.collections.specialized.hybriddictionary.aspx
Dotnet 1.1-4.5
Changes to a ListDictionary if the items are few and a Hashtable if they are many. “Few” and “many” has a breakpoint around 10.
One can change if comparision is case sensitive or not.
The key cannot be null.
http://msdn.microsoft.com/en-us/library/system.collections.specialized.stringcollection.aspx
Dotnet 1.1-4.5
Optimised for string lists.
One can store null, allows duplicates, case sensitive comparision; just the same as List<string> but supposedly faster. If someone had some performance figures or reverse engineered code we might know.
http://msdn.microsoft.com/en-us/library/system.collections.specialized.stringdictionary.aspx
Dotnet 1.1-4.5
Implemented as hash table. Case insensitive comparision. I haven’t checked but I suppose it does ToLower or ToUpper on the keys before storing them. At least that is what I should have done.
StringDictionary is generic and I suppose it exists solely because generics didn’t exist in Dotnet 1.1 and instead of everyone writing their own StringDictionary with their own casts Microsoft built it for everyone (and for themselves of course).
http://msdn.microsoft.com/en-us/library/system.collections.sortedlist.aspx
Dotnet 1.1-4.5
Generic list. Do your own type casting.
http://msdn.microsoft.com/en-us/library/f7fta44c(v=vs.80).aspx
Dotnet 2-4.5
Generic version. Do your own type casting. And debug your own bugs.
http://msdn.microsoft.com/en-us/library/xfhwa508(v=vs.80).aspx
Dotnet 2-4.5
Is this really correct? Didn’t we have Dictionary in dotnet 1 and 1.1? I vividly remember writing my own version (see StringDictionary) for every type I had.
Which brings me to that it isn’t very difficult inheriting from Dictionary and overriding the right methods. There is (at list was back in last century) cookbooks for this on the web. Today I just use List<T> and am happy with it.
http://msdn.microsoft.com/en-us/library/bb353005
Dotnet 3.5-4.5
I have not experimented with this one.
IList is the interface behind List<T>. Use it when you can.
Especially when returning a List, return IList instead to get more decoupling. Especially especially when writing a framework.
http://stackoverflow.com/questions/400135/c-sharp-listt-or-ilistt
https://docs.microsoft.com/en-us/dotnet/api/system.collections.arraylist
https://docs.microsoft.com/en-us/dotnet/api/system.collections.hashtable
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ireadonlylist-1
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ireadonlydictionary-2
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.ireadonlycollection-1
https://docs.microsoft.com/en-us/dotnet/api/system.collections.queue
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.queue-1
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.iset-1
https://docs.microsoft.com/en-us/dotnet/api/system.collections.stack
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.stack-1
This class does not reside in any collection namespace but is still considered a collection since it implements IList. But at the same time it is fixed in size.
If I understand the dox correctly it is the base class for anything Collection but we, as external developers, should not use it; it is solely for the langauge and the compiler people.
It contains a IsFixedSize property which always is True.
https://docs.microsoft.com/en-us/dotnet/api/system.array
These tips come from Gary Short unless noted.
Boxing/unboxing takes time so if you have value types (int, char etc) (not string that even though it behaves like a value type isn’t one) use generic collections instead.
My comment: casting can fail runtime but un/boxing through, say, List<T> never does so 99 of 100 times I prefer the performance penalty. I also have no figures on the costs. Someone?
All lists, except LinkedList has O(1) for adding an item unless it results in growing when we get O(n). LinkedList never grows in chunks and always have O(1). Se more about growing under List<T>.
List<T> sorts slower when the list is almost sorted and slowest when it is already sorted. This is not schtoopidity but a drawback of the quicksort algorithm.
SortedList<T> uses less memory than SortedDictionary<T> but the latter has faster add/remove.
The cast of Gary Short at Öredev is found here.
More info on collections is found here:
I have since the birth of dotnet missed the possibility to have a function inside a function like one can in Pascal.
With lambda, and possibly Dotnet4(?) it is possible. Below is a rather stupid example.
1 2 3 4 5 6 7 8 | internal int AddMaxWierd( int x, int y ) { Func Max = delegate( int a ){ return Math.Min( a, 10 ); }; return Max(x) + Max(y); } |
If the inner method doesn’t have a return value, use “Action” instead of “Func”.
See how there is only one Manipulate method in the class, the other Manipulate method is hidden within the method.
1 2 3 4 5 6 7 8 9 10 11 12 | internal void Manipulate( CustomerList Customer customers ) { Action<Customer> Manipulate = delegate( Customer customer ) { // do stuff... }; foreach( var customer in customers ){ Manipulate( customer ); } } |
Update:
In C#7 it can be done. https://github.com/dotnet/roslyn/issues/6505
Cccommunicate news letter is out.
I proudly copied the head line from the orginial article since I couldn’t make it any better.
The link below leads to a lengthy, but still to the point, text about how to design your exceptions. The examples are from dotnet but the design can be used in, say, Java too.
( I used to have a design pattern for exceptions but I gave it up some time ago and thankfully never blogged about it. )