Click here to Skip to main content

Comments by Erich Ledesma (Top 5 by date)

Erich Ledesma at 6-Jul-11 14:55pm View
   
Deleted
Separator is a string, so it's already "escaped". string.Join does work with char.
 
Thanx for the comment
Erich Ledesma at 4-Jul-11 16:46pm View
   
Deleted
Reason for my vote of 1
As Piebald says: The lock is wrong, and that return null statement will prevent from returning the right instance. Your method would return the right value just once. Sorry mate, but you're spending everyone's time, you should pay attention to what people take the time to write to you.
Erich Ledesma at 28-Jun-11 8:57am View
   
Deleted
Thanx mate. The idea is always trying to make it as simple as posible. And never doing something for no reasson, meaning you might need to undo it latter.
Erich Ledesma at 28-Jun-11 8:45am View
   
Deleted
I agree, it could be generic, and would be usefull. But in most cases you won't need it, and it wouldn't be clear a Join() for something else. In those cases, if you need to join strings for other object types. You could always use a Select() first to convert to string, then join them.
 
The point is. Is just a matter of taste. I like it this way, but that just me.
Erich Ledesma at 9-Jun-11 4:27am View
   
It won't. You're right. Didn't see the tag. Thanx. I'm removing the solution....

Advertise | Privacy | Mobile
Web01 | 2.8.140916.1 | Last Updated 1 Jan 1900
Copyright © CodeProject, 1999-2014
All Rights Reserved. Terms of Service
Layout: fixed | fluid