« first day (2781 days earlier)      last day (399 days later) » 

12:01 AM
REFRESH!
[Minesweeper] 74 Games Played. 47 Bombs Used. 8423 Moves Performed. 20 New Users
[rubberduck-vba/Rubberduck] 3 additions. 3 deletions. 3 commits. 2 issue comments
[Zomis/zomis.github.io-source] 6 additions. 9 deletions. 1 commits
[Zomis/Games] 28 additions. 56 deletions. 4 commits
 
 
7 hours later…
6:51 AM
 
 
2 hours later…
9:08 AM
[1/2] Hello. I was just reading the the most popular regex VBA answer and happened to notice the most popular comment underneath it mentions that Set <object> = Nothing is stated as being required to avoid out
of memory exceptions https://stackoverflow.com/questions/22542834/how-to-use-regular-expressions-regex-in-microsoft-excel-both-in-cell-and-loops#comment46300969_22542835. Discussions such as in this Q&A https://stackoverflow.com/questions/517006/is-there-a-need-to-set-objects-to-nothing state to use this method as VBA de-referencing can be inaccurate.
[2/2] The first link is from 2014 and I am pretty sure there hasn't been development since then. I also thought Set <object>=Nothing wasn't needed (particularly in the given example) as the reference counter will take care of this when Sub out of scope. Can I mark this comment as no longer needed on the basis of not accurate?
Set <object> = Nothing right before End Sub is still very popular in answers I see
 
 
1 hour later…
10:34 AM
IINM that is a Cargo Cult relic that has some reasonable roots in unmanaged objects not fully integrating with that reference counting mechanism.
but that could be wrong
 
 
4 hours later…
2:48 PM
@QHarr as is declaring locals As New :(
I almost spilled my coffee reading the latest comment on tB array initialisation. So much energy spent advocating against any kind of evolution of the language, only to now dismiss square brackets as a breaking change. Geez.
 
 
4 hours later…
7:17 PM
@MathieuGuindon Aye. So what are the occasions where Set object = Nothing might be needed? Just read your comment there.
 
 
3 hours later…
10:15 PM
> The code inspector type "member 'Range' implicitly references 'ActiveSheet'" wrongly applies to
`range(wks.cells(1,2), wks.cells(1,2))`
as in this case range implicitly reference wks, or atleast this is what it seems to me since it's working on wks even if activesheet is different than wks,

(also see your examples here: https://rubberduckvba.com/inspections/Details/ImplicitActiveSheetReference?example=1#examples)
 
10:41 PM
> As far as I can tell the `Range` property is indeed implicitly qualified in that instruction, which makes me expect error 1004 whenever the active sheet isn't `wks`, unless written in the code-behind of that specific worksheet.

Note that the example is *explicitly* qualifying the `Range` call while implicitly qualifying the inner `Cells` calls, which is the inverse situation, but both `Range` and `Cells` are properties of `Worksheet`, and the inspection is - correctly - flagging implicit refe
 
@QHarr if and when not doing it causes problems, in which case I'd expect a comment to explain why the object needs to be explicitly destroyed!
 
 
1 hour later…
11:45 PM
[rubberduck-vba/Rubberduck] 1497 stars vs. [decalage2/oletools] 1884 stars
 

« first day (2781 days earlier)      last day (399 days later) »