notepad is for noobs - real pros' use edlin...
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Object Oriented Development vs Practicality
Collapse
X
-
-
You're all wooses - I use VS 1978 Punch Card version!If you think my attitude stinks, you should smell my fingers.Comment
-
Use I do turn it off because I always get the cranky workstations to work with which lag seriously the moment you hit ".".
Atw: I can remember the members, properties and methods. And you shouldn't be using globals!Serving religion with the contempt it deserves...Comment
-
-
About 80% - SDK documentation for the restOriginally posted by DiestlAll of them in the whole .net Framework?
Serving religion with the contempt it deserves...Comment
-
Why is that? Are you aware of the kind of performance penalty you get if you use property accessors rather than global variable (in a class)?Originally posted by TheMonkeyAtw: I can remember the members, properties and methods. And you shouldn't be using globals!Comment
-
Yeah. Performance isn't always key though...Originally posted by AtWWhy is that? Are you aware of the kind of performance penalty you get if you use property accessors rather than global variable (in a class)?Serving religion with the contempt it deserves...Comment
-
A lot of properties are just read/write without any modifications and checks (like ranges etc), ie:Originally posted by TheMonkeyYeah. Performance isn't always key though...
class foo
{
public int property
{
get { return _property; }
set { _property=value; }
}
int _property=0;
}
In such case there is absolutely no need to have property.
Accessing value via accessor rather than directly is (I think) over 10 (!) times slower - performance killer in tight loops.Comment
-
Yeah true but most business tier stuff has validation in it anyway. In the case above just having a public member variable will do.Originally posted by AtWA lot of properties are just read/write without any modifications and checks (like ranges etc), ie:
class foo
{
public int property
{
get { return _property; }
set { _property=value; }
}
int _property=0;
}
In such case there is absolutely no need to have property.
Accessing value via accessor rather than directly is (I think) over 10 (!) times slower - performance killer in tight loops.
Killer is:
object.Property += 1;
Kills the thing quite badly.Serving religion with the contempt it deserves...Comment
-
Comment
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers

Comment