« first day (490 days earlier)      last day (2690 days later) » 

00:01
RELOAD!
[Phrancis/ChucK-Scripts] 1 commit. 8 additions. 5 deletions.
[retailcoder/Rubberduck] 4 commits. 310 additions. 239 deletions.
[rubberduck-vba/Rubberduck] 6 commits. 3 opened issues. 1 closed issue. 18 issue comments. 619 additions. 477 deletions.
[Vannevelj/VSDiagnostics] 1 opened issue. 3 issue comments.
00:26
Thanks @AndrewM Mug worked hard to get the parsing speed reasonable for such large projects. I used to have a project about that size. =)
01:09
@RubberDuck it's still too slow!
I think I can get the identifier resolution to run asynchronously
That should considerably speed things up
 
2 hours later…
02:53
@Mat'sMug Now you have n problems.
 
3 hours later…
05:42
woopsie
#MoreLikeIt
yes, these are progress bars
yes, I still need to figure out how I'll get them to update
no, the thing isn't working yet
but damn, looks great :)
TTGTB
[retailcoder/Rubberduck] retailcoder pushed commit 7fd2289c to next: Identifier reference resolution is now asynchronous. yay!
[retailcoder/Rubberduck] retailcoder pushed commit c6252956 to next: moved ProgressDialog to new Rubberduck.UI.ParserProgress namespace
[retailcoder/Rubberduck] retailcoder pushed commit a4ed19da to next: added ParserProgressControl - it's not parsing anything yet, but it looks great!
06:14
[retailcoder/Rubberduck] retailcoder pushed commit d6944eaf to next: ProgressDialog closes when parsing completes.... but XAML control doesn't have time to display...
 
5 hours later…
11:27
> Glad to see that is on the list. Some of my code is nested to 9+ levels and I am just learning how to flatten it out. Currently I am using a freeware tool called SourceMonitor (TM) Version 3.5 from Campwood Software to detect these issues. It is worth a look at this little application if you have not seen it at it generates a range of metrics for VB.
11:43
> I mostly get this kind of error from setting up a do until .EOF loop for a recordset and forgetting to put in a .movenext.
12:06
> Ms-access is the domain of professionals who code not coding professionals so I think a manual is crucial. I would hope that the rest of the community could assist the the manual (including myself), to keep the main team members free for development.
4
@Duga I like this guy
> @AndrewM- also consider selecting an inner block of code, and then right-click > refactor > extract method :-)
12:39
> I am just trying to reconcile how unit testing fits in with making backups of the accdb file using the build in backup function. I use the backup function everyday before settling down to write code. If there was an internal table in the database which had the commit history, then I could see when I created a backup that matched the commit. Currently I am using Git for diffing to find out what I changed between backups. It might be a stopgap until Git integration is fully implemented. I mi
12:55
> So there's separate kinds of infinite loops:

- loops that have a constant end condition, that is never true (e.g. `while true`)
- loops that have an end-condition that never becomes true (e.g. never advancing a recordset)

The earlier kind can be rather simply found by the Parser. In case of more complex expressions you could try to evaluate the loopcondition down.

The latter kind requires more intrinsic knowledge of the context. What's necessary here is a more in-depth analysis (thin
13:15
> @Vogel612 even constant condition is trickier than it looks, mostly because VBA's lowest scope level is at the procedure level - it would be simpler if a For loop defined a scope.. we might have to simulate that to achieve proper inspection of variable references.
14:13
> We're getting into semantic analysis at this point. Are we in a position to really do that?
> @ckuhn203 not reliably. But we can try and pick up the obvious ...although usefulness (of picking up blatantly infinite loops) vs. effort required makes this a not very much appealing feature to build.
 
4 hours later…
18:16
Developers: How to easily save time http://www.commitstrip.com/2015/10/09/developers-how-to-easily-save-time/ http://t.co/8vKjxocUEG
Identifier resolution will be running async in v2.0, so expanding progress details is really for large #VBA projects http://t.co/DqdziJHOtl
 
5 hours later…
23:39
> I was storing the entire database in Git including table defs, query defs and form set up code. One of the main issues was that Git is case sensitive. For some reason, capitalisation in my code often changes by itself despite option explicit being used everywhere. That meant that most of the changes flagged by diffing were nonsense. The second issue is mainly related to procedures that are too big which resulted in nearly all of the procedures changing with every check-in. As a result of
23:50
> I have been developing in ms-access since 1.0 and write big applications. However programming has evolved and I am finding myself encountering rafts of concepts that are ported in from other environments. Use of the MVC development patten was promoted by one of the lead RD developers and was actually how I found RD. Yesterday, I came across valuable comments on Hungarian notation, flattening of unnecessary nesting and quite a bit more. These things might be intuitive to highly experienced

« first day (490 days earlier)      last day (2690 days later) »