-
Recent Posts
Recent Comments
- mohamed on FieldByName, FindField: too convenient to be honest
- J.-G. Yu on Using Richedit 4.1 with D2010
- J.-G. Yu on Using Richedit 4.1 with D2010
- J.-G. Yu on Using Richedit 4.1 with D2010
- Jochen S. on The Unfortunate Effect of WM_SETREDRAW
Tags
- $Message
- A little bit of zis
- AutoSave
- Best practices
- Bug
- Code Camp
- CodeWay
- Coding standard
- ComCtrls
- Community
- Compiler directive
- Conference
- Configuration
- Data
- Debugger
- Delphi
- Explorer
- FieldByName
- IDE
- inherited
- Jobs
- LockWindowUpdate
- Maps
- Memory Leaks
- Meta
- Motorcycle
- Optimization
- Personal
- Quality
- Readers
- Resources
- RichEdit
- SendTo
- shell
- Sounds
- Speech
- Statistics
- TIOBE
- UI
- User Interface
- VCL
- Warnings
- Windows
Archives
Categories
Blogroll
Meta
Tag Archives: Quality
When The Debugger Leaks…
… you may end up chasing memory leaks that don’t exist. I was at work investigating some bizarre behavior of our application when dealing with a big customer file and I had ReportMemoryLeaksOnShutdown turned on as it was very likely … Continue reading
Posted in Debugger, Delphi, Quality
Tagged Bug, Debugger, Delphi, IDE, Memory Leaks, Quality
22 Comments
A little bit of zis, etc.
I haven’t blogged in quite a while… I have been busy at work and at home. And now I’m with the family for an extended week-end in the mountains. So, this post will be more like a pot-pourri of little … Continue reading
FieldByName, FindField: too convenient to be honest
I don’t know about you, but I can’t count anymore the number of times I’ve seen this code pattern (in code snippets online as well as in production code): while not ADataSet.Eof do begin […] ADataSet.FieldByName(‘MyFieldName1’).SomePropertyOrMethod; ADataSet.FieldByName(‘MyFieldName2’).SomePropertyOrMethod; […] ADataSet.Next; end; … Continue reading
Posted in Coding standard, Delphi, Quality
Tagged Best practices, Coding standard, Delphi, FieldByName, Optimization, Quality
36 Comments
Hints and Warnings begone!
This previous post has stirred some interesting comments and reactions (thank you!). I would like to come back on the “no Hint, no Warning policy” and why I like it, but without the need to be zealot. Why desirable? The … Continue reading
Posted in Coding standard, Delphi, Quality
Tagged Best practices, Coding standard, Compiler directive, Delphi, Quality, Warnings
4 Comments
Don’t Do Evil to Users
vs “Your work will self-destruct in five seconds…” With Delphi (or C#) it’s so easy to put a Timer to implement some Auto-DoStuff feature that you’ll find one in almost any application. No doubt it can be very handy; it … Continue reading
Programmers are only as good as what their users can get
What matters for your users is that your software helps them get their job done efficiently, correctly and reliably. They do not care what language you used, how elegant your code is, that your new super-sort algorithm is faster than quick-sort … Continue reading