automatic-properties

I would like to plot a number of 3D graphs from different data files. For example I am using fid = fopen('SS 1.dat','r'); to read the first file and then plot a graph. How to set the program to change the name to 'SS 2.dat' automatically? Also for the tenth file the name becomes 'SS 10.dat' which has one space less (i.e.only two space between SS and 10) then the first to ninth files. How to set the program to adjust for that? Thank you. The following code displays a lazy way to print the names from 1 to 999 that you mentioned: for ii=1:999 ns = numel(num2str(ii)); switch ns case 1 fname = ['ss

I need to create and manage many simple published properties. I call them auto-properties if they look like that: private FTitle: string; published property Title: string read FTitle write FTitle; Usually I create them next way: Adding property name and type: property Title: string Selecting and copying property name Title to clipboard. Appending the line with read F Ctrl+V write F Ctrl+V ; Pressing Ctrl+Shift+C and this will generate the private field Is there any way to exclude steps 2 and 3 to add properties faster? Maybe it is possible to create some macro for this? Stefan Glienke Since

Consider this: public class interface Person : IPerson { int ID { get; protected set; } string FirstName { get; set; } string LastName { get; set; } string FullName { get { return FirstName + " " + LastName; } } } And this: public class StubPerson : IPerson { int ID { get { return 0; protected set { } } string FirstName { get { return "Test" } set { } } string LastName { get { return "User" } set { } } string FullName { get { return FirstName + " " + LastName; } } } Usage: IPerson iperson = new Person(); Or: IPerson ipersonStub = new StubPerson(); Or: IPerson ipersonMock = mocks.CreateMock

I recently found out about auto-properties and like them quite a lot. At this moment I am trying to use them everywhere where I can. Not really to just be able to use them everywhere, but more to see how well they work in most situations. Now I am making a singleton and thought:"Hey, let's try auto-properties here as well". public class MySingleton { public static MySingleton MySingleton { get; private set; } private MySingleton() {} static MySingleton() { MySingleton = new MySingleton(); } } So my question is: "Is it a good idea to implement a singleton like this?" I am not asking whether a

Automatic properties let me replace this code: private MyType myProperty; public MyType MyProperty { get { return myPropertyField; } } with this code: public MyType MyProperty { get; private set; } with a few changes here and there - but is there a way to replace this code: private readonly MyType myProperty; public MyType MyProperty { get { return myPropertyField; } } with something similar? No, but this idea is being tracked on Connect . Indeed, there is no way to do this at present. We realize that in C# 3 we produced a bit of a philosophical oxymoron. The design of LINQ is heavily steeped

If both get and set are compulsory in C# automatic properties, why do I have to bother specifying "get; set;" at all? ERROR: A property or indexer may not be passed as an out or ref parameter If you didn't specify {get; set;} then the compiler wouldn't know if it's a field or a property. This is important becasue while they "look" identical the compiler treats them differently. e.g. Calling "InitAnInt" on the property raises an error. class Test { public int n; public int i { get; set; } public void InitAnInt(out int p) { p = 100; } public Test() { InitAnInt(out n); // This is OK InitAnInt(out