« first day (768 days earlier)      last day (2412 days later) » 
00:00 - 22:0022:00 - 00:00

12:01 AM
RELOAD!
[Hosch250/Rubberduck] 43 commits. 5512 additions. 1763 deletions.
[rubberduck-vba/Rubberduck] 29 commits. 12 opened issues. 10 closed issues. 34 issue comments. 2540 additions. 798 deletions.
[Vogel612/TranslationHelper\‌​] 3 commits. 20 additions. 95 deletions.
[Hosch250/Rubberduck] build for commit 3be14625 on reinstateParseTreeInspections: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 3be14625 on unknown branch: AppVeyor build succeeded
 
@Duga I guess I win, but I'm pretty sure most of those commits are from my many branches.
2.0 is 93% done.
33 open issues.
A couple of them I wouldn't have any issues at all delegating to 2.1, or maybe 2.0.{stable + 1}
 
12:25 AM
Working on fixing the non-working Ignore annotations.
 
Actually, that isn't the write way to do it (TM)
 
[Hosch250/Rubberduck] Hosch250 pushed commit f70bfc29 to reinstateParseTreeInspections: Fix a bunch of ignored ignore annotations for parameter inspections
Revert "Fix a bunch of ignored ignore annotations for parameter inspections"

This reverts commit f70bfc29785c546f11063ea5b7fda6f9401ec378.
[rubberduck-vba/Rubberduck] build for commit f70bfc29 on unknown branch: AppVeyor build succeeded
 
@Mat'sMug He has to click the "Include" button...
 
[Hosch250/Rubberduck] build for commit f70bfc29 on reinstateParseTreeInspections: AppVeyor build succeeded
 
12:41 AM
He probably wants to keep them in separate repos.
 
[Hosch250/Rubberduck] Hosch250 pushed commit 45603205 to reinstateParseTreeInspections: Re-fix ignoring parameter inspections
[rubberduck-vba/Rubberduck] build for commit fa018b05 on unknown branch: AppVeyor build succeeded
[Hosch250/Rubberduck] build for commit fa018b05 on reinstateParseTreeInspections: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 45603205 on unknown branch: AppVeyor build succeeded
[Hosch250/Rubberduck] Hosch250 pushed commit f0b7706c to reinstateParseTreeInspections: Fix crash in Change Procedure to Function quick fix
[Hosch250/Rubberduck] build for commit 45603205 on reinstateParseTreeInspections: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit f0b7706c on unknown branch: AppVeyor build succeeded
[Hosch250/Rubberduck] build for commit f0b7706c on reinstateParseTreeInspections: AppVeyor build succeeded
 
12:58 AM
Not to start an argument but please tell me what difference do you see in the output for MsgBox TypeName(Format(Date, "mmddyy")) and MsgBox TypeName(Format$(Date, "mmddyy")). Also there's no advatange of type conversion in terms of performance, run a loop between date1 = #1/1/2008# and date2 = #1/1/3020# with and without $, you will get the same run-time. so why use $. Its looks fancy, no doubt there. but thats it in this case.:) — cyboashu 18 mins ago
 
@ThunderFrame You tell him.
It's amazing how many bugs there are in even the well-tested inspections.
 
> I use an old machine for performance tests.
W81 x32, 3GB Ram, Access 2010 x32.
Rubberduck 2.0.5.34977 takes ~1 minute to parse my project.
![capture34](https://cloud.githubusercontent.com/assets/140737/16788563/fdc9e748-485a-11e6-8678-651c5cbdc51f.PNG)
> In other words, Windows starts a bunch of threads to handle our parsing/resolving/inspecting needs that fast?
 
I think we knew that...
 
1:21 AM
[Hosch250/Rubberduck] Hosch250 pushed commit 21b4990e to reinstateParseTreeInspections: Fix bug in Pass Parameter by Value quick fix
 
See you tomorrow.
 
> Closed down. Tried again. This time it took ~3 minutes to be ready.
Log is here.

[rubberduck.zip](https://github.com/rubberduck-vba/Rubberduck/files/360533/rubberduck.zip)
[Hosch250/Rubberduck] build for commit 21b4990e on reinstateParseTreeInspections: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 21b4990e on unknown branch: AppVeyor build succeeded
> Clicked the Add-In button and it crashed Access. Updated log here.

[rubberduck.zip](https://github.com/rubberduck-vba/Rubberduck/files/360540/rubberduck.zip)
 
1:44 AM
@Hosch250 aye.. I remember struggling to see that button the first time. I think it needs an icon.
 
 
3 hours later…
5:06 AM
@Comintern hey, saw the topic about sendkeys, got a thread of ideas with it. My existing VBA code has lots and lots of send keys which @Mat'sMug mentioned was interesting. I am at work so I don't have the code but you might hate me for it later. ;)
 
 
4 hours later…
8:54 AM
> I try to publish my existing repository to a remote location:

![image](https://cloud.githubusercontent.com/assets/10561922/16797426/cc332b58-48e7-11e6-9c96-7408fa0d8850.png)

I succeeded to set up the proxy settings via tortoise-git and i can access the remote repo via GitGui.
 
 
2 hours later…
10:43 AM
> When executing this code in Access 2016 32-bit.
```vb
Dim rd As Rubberduck.ParserState
Set rd = New Rubberduck.ParserState

rd.Initialize Application.VBE
rd.Parse
'...
```

Run-time error: '-2146233088 (8131500)
"One or more errors occurred"
![parse](https://cloud.githubusercontent.com/assets/16574009/16800626/8549413a-4939-11e6-9cd9-393c69e90d8f.png)

If I choose `Debug`, the active line is `rd.Parse` and then Step Into the code, the line succeeds and the code can ca
 
10:58 AM
> The `AllDeclarations` property returns an Array of `IDeclaration`, but the array cannot be indexed. A `For Each..Next` loop can iterate the array members, but a `For..Loop` cannot:

The Rubbderduck Type Library doesn't allow me to declare a variable of type `IDeclaration`

```vb
Dim rd As Rubberduck.ParserState
Set rd = New Rubberduck.ParserState

rd.Initialize Application.VBE
rd.Parse

'This works, but decl must be a variant
Dim decl As Variant
For Each decl I
 
11:12 AM
> The DeclarationType enumeration doesn't seem to have a CoClass member.

Maybe I'm doing it wrong, but I'm trying to find the events that a an object implements.

For example, in Excel, to find the events for the Worksheet CoClass, I need to find the `DocEvents` interface and enumerate the DocEvents members, but currently, it seems that `AllDeclarations` does not return any details about the relationship between `Worksheet` and `DocEvents`
 
11:37 AM
> Does the API let you access the events under Workbook? Not much care was given to the COM API when we started adding support for this in Rubberduck itself.
[rubberduck-vba/Rubberduck] Hosch250 pushed commit d6fe381c to next: Close #1973
[rubberduck-vba/Rubberduck] web-flow pushed commit dc4b004d to next: Merge branch 'next' into Issue1973
[rubberduck-vba/Rubberduck] web-flow pushed commit 9b01756f to next: Merge branch 'next' into Issue1973
Merge pull request #2036 from Hosch250/Issue1973

Find Symbol bug fixes
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 4947e80a to next: Reinstate parse tree inspections
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 3be14625 to next: Merge branch 'next' of github.com/rubberduck-vba/Rubberduck into reinstateParseTreeInspections
[rubberduck-vba/Rubberduck] Hosch250 pushed commit f70bfc29 to next: Fix a bunch of ignored ignore annotations for parameter inspections
Revert "Fix a bunch of ignored ignore annotations for parameter inspections"

This reverts commit f70bfc29785c546f11063ea5b7fda6f9401ec378.
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 45603205 to next: Re-fix ignoring parameter inspections
[rubberduck-vba/Rubberduck] Hosch250 pushed commit f0b7706c to next: Fix crash in Change Procedure to Function quick fix
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 21b4990e to next: Fix bug in Pass Parameter by Value quick fix
Merge pull request #2039 from Hosch250/reinstateParseTreeInspections

Reinstate parse tree inspections
[rubberduck-vba/Rubberduck] build for commit 7a9192a4 on next: AppVeyor build succeeded
> No, the events aren't under Workbook. For example, the SheetBeforeRightClick Workbook event appears as a member of the WorkbookEvents declaration and the IWorkbookEvents declaration, but not under the Workbook declaration.
[rubberduck-vba/Rubberduck] build for commit 40d777ad on next: AppVeyor build succeeded
> Actually, it doesn't look like I can even find the members of Workbook (or any CoClass)
 
12:35 PM
> For example, the Workbook property BuiltinDocumentProperties' has a parent declaration of _Workbook`
> For example, the Workbook property BuiltinDocumentProperties has a parent declaration of _Workbook and _Workbook has a parent declaration of Excel
 
@PeterMTaylor I have no problem with using SendKeys if you need to use SendKeys. Granted using the Windows API is preferable if you can get a handle to a control, otherwise, meh.
 
 
1 hour later…
1:52 PM
Without thinking about it, I refactored a couple of procedures into a module and gave the module the same name as one of the procedures.
I now get a compile error "Expected variable or procedure, not module" which doesn't seem unreasonable.
When I renamed the module the calls to the procedure also got renamed.
Not sure if that can be prevented, but it seems to me that there's enough info stored to allow RD to differentiate, even if the compiler cannot.
 
2:17 PM
the basic assumption in RD is that the code we're resolving is compilable. there's not really a way around that... if VBA can't understand it, RD shouldn't be expected to
 
> The following functions have a `Variant` "date" parameter:

```VB
DateAdd
DateDiff
DatePart
DateValue
Day
CDate
FormatDateTime
Hour
Minute
Month
Second
TimeValue
Weekday
Year
```

The problem is that when they are passed a `String`, it is converted to a `Date` based on the system's locale settings. I'd generally consider this an error personally, because it can break code in unpredictable ways if the locale changes.

The ones above are fairly straight-forward - `Format`
> Hi!
I'd like to use this amazing package in MS Access but unfortunately, it almost always crashes Access when I quit the application. I'm able to reproduce the problem in many specialized/slim dev vms I'm using for VBA programming without issues when this tool is not installed. These VMs are composed of different OS (x64) / Office (x32) / SQLServer (x64) versions and fully patched.

How can I help troubleshoot this problem?

Thanks in advance for you help.

ubidev
 
@Mat'sMug le sigh... I suppose it's my fault in the first place for the naming confusion.
 
> @Hosch250 mentioned in #1190 that the crash on exit will be addressed soon. That's for excel, but I assume that Access has the same underlying problem and will be fixed, too.
> IIUC the inspection would find calls to these functions, locate the first argument and trigger an inspection result when that argument is any expression known to be of a String type (e.g. a string literal, or a string variable, or a string constant expression) - handling string literals and known-to-be-string variables is going to cover 99% of the cases, so I wouldn't worry much about the complexity of the remaining cases, that can always be fine-tuned later.
 
@FreeMan yep! ;0)
 
2:45 PM
> Also, it would be super handy to force a reparse and a refresh of the CE (if it's displayed).
 
3
Q: Trying to make more simple VBA

DiogoI have few models like this below for diferent tools i manage. I am trying to clean/improve the code... Could you help me? All the informations comes inside columns B to N, and the column P concatenate it with ";". There are 6 sheets i do the same thing. Any ideas to have a better performance a...

 
 
I guess I'll work on the inspections more.
I should probably fix the resolver, but I don't like doing that :(
 
Sounds like more fun than parsing butchered Mexican addresses...
 
Maybe.
Want to swap?
Actually, installing VS U3P1.
 
> Just tested it - it seems the VBE's Project Explorer *does* support importing multiple files at once, via drag-and-drop.

FWIW Rubberduck's Code Explorer supports importing multiple files at once, via the regular "import" command.
 
It actually isn't too bad if they had at least a tiny clue about Latin American address formats.
 
3:52 PM
> Yeah, we need to re-write pretty much the entire COM library from scratch--and put it in its own project too, I'd recommend.
 
Ugh. It doesn't help that there's a town in Missouri named Mexico...
 
> @Hosch250 actually, I'd rather not have too many type libraries floating around. IMO best-case scenario is VBA code can reference Rubberduck.tlb and get everything we have to offer right there. Also the Rubberduck.API namespace is brand new, off the 2.0 parser code.
> @Hosch250 actually, I'd rather not have too many type libraries floating around. IMO best-case scenario is VBA code can reference Rubberduck.tlb and get everything we have to offer right there. Also the Rubberduck.API namespace is brand new, off the 2.0 parser code. Experimental though.
 
@Comintern Apparently, it is up to me to expose Rubberduck to the VBE through COM.
I think I'll be needing some help here.
 
OK. There are a couple marshaling things to watch out for, but it shouldn't be too bad.
 
I'm still tackling other bugs, so I won't be doing this for a couple days, probably.
It seems like parts of RD are release-ready, and other parts are a long way away still.
 
4:02 PM
> After opening the code explorer for the first time. If you right click on an empty space without selecting a project beforehand. an error is raised.
> Whoops, I thought I'd fixed that.
> Whoops, I thought I'd fixed that. If there is only one project, it should offer to import, if there are 2+ projects, it doesn't know which to import to, so it should be disabled.
> @ThunderFrame why iterate an object collection with a `For` loop, when a `For Each` loop is known to be faster? I agree there is a bit of marshaling tweaks to be done here (it's annoying that you need a `Variant` there), and yes indeed `LBound`/`UBound` *should* work.

Also note the `ParserState` events don't work for now because of a threading issue, ref. #1239.
> @Hosch250 if there are 2+ projects, one of them must be the VBE.ActiveProject - that's where it should import to.
> @Hosch250 if there are 2+ projects, one of them must be the VBE.ActiveVBProject - that's where it should import to.
> Nope, the ActiveVBProject can be null.
> But we should be checking for that before dismissing the option of importing. Are we?
> Working on it. Right now, we import to the project containing the selected node. This is what I'm going to make it do:

1) Selected node's project
2) Single project
3) Active project
 
:+1:
 
Merge pull request #2036 from Hosch250/Issue1973

Find Symbol bug fixes
Merge pull request #2039 from Hosch250/reinstateParseTreeInspections

Reinstate parse tree inspections
[Hosch250/Rubberduck] Hosch250 pushed commit e506ffa7 to Issue2048: Close #2048
 
We busted issue 2^11.
3
 
> Close #2048
[Hosch250/Rubberduck] build for commit e506ffa7 on Issue2048: AppVeyor build failed
BUILD FAILURE!
[rubberduck-vba/Rubberduck] build for commit e506ffa7 on unknown branch: AppVeyor build failed
BUILD FAILURE!
 
4:21 PM
Three compilation errors in the tests :(
 
[Hosch250/Rubberduck] Hosch250 pushed commit 894d74fc to Issue2048: Fix broken tests
[Hosch250/Rubberduck] build for commit 894d74fc on Issue2048: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 894d74fc on unknown branch: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] Hosch250 pushed commit e506ffa7 to next: Close #2048
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 894d74fc to next: Fix broken tests
Merge pull request #2049 from Hosch250/Issue2048

Fix crash in CE import command
 
4:42 PM
[rubberduck-vba/Rubberduck] build for commit 7b0a9b89 on next: AppVeyor build succeeded
 
@Mat'sMug Our Ignore functionality is pretty crude.
 
meaning?
 
We can't ignore a single parameter inspection, for example, without disabling them all for the function/proc.
'@Ignore ConstantNotUsed
Const foo As Integer = 4, buzz As String = "ftesti"
That disables the inspection for both of those.
In fact, that doesn't even work in Next--I just caught the bug.
And not all of the inspections offer Ignore that should. I'll add it to them.
 
[Hosch250/Rubberduck] Hosch250 pushed commit 675c07c9 to inspectionBugs: Give declarations for consts have annotations
[Hosch250/Rubberduck] build for commit 675c07c9 on inspectionBugs: AppVeyor build succeeded
 
4:57 PM
@Hosch250 then they should be parameterized?
'@Ignore ConstantNotUsed("foo")
 
Something like that.
 
gets painful to maintain though
 
What about this one?
 
then you want to ignore "buzz" and need to edit to:
 
'@Ignore UseMeaningfulName
Sub f(f)
End Sub
 
4:58 PM
'@Ignore ConstantNotUsed("foo", "buzz")
@Hosch250 oh that's plain bloody evil
 
@Mat'sMug pats self on back
 
besides, if f is a bad name for a method, f is just as bad a name for a parameter anyway
 
Right, but ignoring one shouldn't ignore the other, or should it?
 
'@Ignore UseMeaningfulName("f")
it will, and I'm fine with that
 
Well, this is going to be a bloody pain fixing.
 
5:02 PM
What about comma delimited instead of parameterized?
'@Ignore ConstantNotUsed, ConstantNotUsed
Const foo As Integer = 4, buzz As String = "ftesti"
 
@Comintern Because that would be awful trying to resolve.
And how are you going to just ignore buzz that way?
 
Hmmm...
Good point.
 
5:14 PM
@Mat'sMug Is there ever a point in which we should not support ignoring an inspection?
We have several that are missing ignore, and some that I'm not sure about (Option Explicit, Malformed Annotation)
Also, we have so many ignores that I'm not sure whether it would be better to add it by default and let the inspection results explicitly disable it or not.
 
@Hosch250 yes
Option Explicit should never be ignored
 
Figured as much.
Ok, here is the list that doesn't support Ignore:
 
MalformedAnnotation is basically a RD compile error, so shouldn't be ignored either
 
AssignedByValParameter
ParameterCanByByVal
SelfAssignedDeclaration
ProcedureCanBeWrittenAsFunction
OptionBase
OptionExplicit
MultipleFolderAnnotations
MultilineParameter
MoveFieldCloserToUsage
MalformedAnnotation
FunctionReturnValueNotUsed
EncapsulatePublicField
EmptyStringLiteral
WriteOnlyProperty
I allowed ignore on AssignedByValParameter, ParameterCanByByVal, and ProcedureCanByWrittenByFunction so far.
 
and it works?
 
5:21 PM
Yeah, I tested them.
 
awesome
with unit tests?
 
I'll leave OptionExplicit, MalformedAnnotation, and MultipleFolderAnnotations.
Not yet.
 
hears frantic typing
 
That's sounds like a better way to get the answers that you are looking for instead of the answers you need. If the dates are stored in Excel as dates and not strings, you can still do lookups with dates or even numbers. — Comintern 1 min ago
How did I let @ThunderFrame drag me into this question...
 
Any others you want to be left, or should I support ignore for the rest?
I take it you want Ignore on the rest then.
@Mat'sMug How do I trigger the SelfAssignedDeclaration inspection?
 
5:30 PM
Dim foo As New Collection
or As New AnyObjectType actually
 
Oh, OK.
 
(must be a local variable)
 
I was trying d = d, or something.
 
We don't have unit tests on any of the Ignores.
I'll do that after lunch.
 
5:51 PM
Manually tested only.
 
[Hosch250/Rubberduck] Hosch250 pushed commit 9ea89cc7 to inspectionBugs: Add a bunch of ignoreonce's to inspection quick fixes
[Hosch250/Rubberduck] build for commit 9ea89cc7 on inspectionBugs: AppVeyor build failed
BUILD FAILURE!
 
@Duga Thank you, sweetie. What now?
Tests are like an ornery wife. They get mad every time you make a minor change.
 
6:09 PM
[Hosch250/Rubberduck] Hosch250 pushed commit 60fe619a to inspectionBugs: Pass state to inspection instead of null in tests.
[Hosch250/Rubberduck] build for commit 60fe619a on inspectionBugs: AppVeyor build succeeded
> Hello
below is the requested log file after the crash of RD 2.0.5.

2016-07-13 19:57:05.3433;ERROR;Rubberduck.Parsing.VBA.ComponentParseTask;Exception thrown in thread 8.;System.Runtime.InteropServices.COMException (0x800A01A8): Exception from HRESULT: 0x800A01A8
at Microsoft.Vbe.Interop._VBProject.get_HelpFile()
at Rubberduck.Parsing.VBA.RubberduckParserState.SetModuleState(VBComponent component, ParserState state, SyntaxErrorException parserError) in C:\Users\hosch\Documents\Vis
> Thanks.
> @eteichm was that at startup, random in the middle of a session, or as you were quitting the host application?
[Hosch250/Rubberduck] Hosch250 pushed commit 02e39f3a to inspectionBugs: SelfAssignedDeclaration tests
 
OK, duck, starting the ignore tests.
 
6:27 PM
[Hosch250/Rubberduck] build for commit 02e39f3a on inspectionBugs: AppVeyor build succeeded
 
6:41 PM
@Mat'sMug - Completely unrelated question. Do you know if the old non-ISO postal abbreviation "PQ" for Québec is still in use, or is that pretty much gone entirely now?
 
They'd probably figure it out, but I'd use "QC"
No idea though
 
I'll add it to my normalizer "corrections" list then. Not sure how I missed that one...
 
6:54 PM
> It was random in the middle of a session.
The Excel file contains a total of 36 modules. I'll provide a longer log file if required.
 
7:08 PM
> @eteichm yeah. seems the few previous log entries would have a clue about what happened. do you have TRACE level enabled?
 
 
1 hour later…
8:15 PM
> @retailcoder because the AllDeclarations property currently returns an array, and a For Loop is generally faster than a For Each Loop, with arrays.
> Yes, I've TRACE and DEBUG level enabled as well. See attached longer log file.
[Rubberduck_crash.zip](https://github.com/rubberduck-vba/Rubberduck/files/362381/Rubberduck_crash.zip)
> @ubidev, If this is what you see then I am having the same problem. RD 2.0.5.34977
![capture42](https://cloud.githubusercontent.com/assets/140737/16818388/50107aa2-48fc-11e6-89df-0050f754d361.PNG)
 
8:38 PM
0
Q: Can UDT's be used as method parameters in any way?

Mat's MugFor years I've been avoiding the use of Public Type UDT's in VBA, because they're hard to pass around and I never really bothered trying to understand why - it was simply easier to just create a class module and work with actual objects instead. But recently I gave it a shot, and once I figured ...

@Comintern if you know the answer.... I'd love to FINALLY understand this. ^^
 
@Mat'sMug - I have some suspicions about the answer...
 
the compiler messages are completely stupid IMO
 
Yes, they are. I suspect it has something to do with how VB uses "temporary" COM registrations for types.
 
8:54 PM
looks like some people don't understand the meaning of "method"
 
> We can offer a quick fix to remove Option Base 1 statements.
> That would be a very dangerous quick-fix, that could instantaneously introduce a pletora of off-by-one errors everywhere in the code. IIRC it was debated at one point, and we decided that the best course of action would be to simply treat the inspection as a warning, a cue to remember "look, it's base 1 here"
> That would be a very dangerous quick-fix, that could instantaneously introduce a plethora of off-by-one errors everywhere in the code. IIRC it was debated at one point, and we decided that the best course of action would be to simply treat the inspection as a warning, a cue to remember "look, it's base 1 here"
> Oh. Makes sense.
 
9:10 PM
Gah! I know I've seen that set of errors before, but now I can't replicate it at all.
This works fine:
'Module1
Option Explicit

Public Type Foo
    Bar As Integer
    Baz As Long
End Type

Private Sub Tests()
    Dim Temp As Class1

    Set Temp = New Class1
    Dim Var As Foo
    Var.Bar = 42
    Temp.FrobTheFoo Var

    Var = Temp.GimmeSomeFoo
    Debug.Print Var.Bar
End Sub
Class1:
Option Explicit

Public Sub FrobTheFoo(ByRef Var As Foo)
    Debug.Print Var.Bar
End Sub

Public Function GimmeSomeFoo() As Foo
    Dim OutVal As Foo
    OutVal.Bar = 666
    GimmeSomeFoo = OutVal
End Function
 
Zak
@Mat'sMug Oh, are methods specifically for objects?
 
yeah
a std module has "procedures" (macros) and "functions" (UDF's); a class module has "properties" and "methods"
although, awkwardly, you could define a property on a std module, too
interesting. if you make the factory method Friend instead of Public, it compiles. too bad that it defeats the purpose
 
Ahhh... you're trying to pass them between projects?
 
@Zak A VBA Module is actually just like a static class in .NET:
'Module1
Option Explicit

Private mFoo As Long

Public Property Let Foo(Var As Long)
    mFoo = Var
End Property

Public Property Get Foo() As Long
    Foo = mFoo
End Property

'Module 2
Option Explicit

Public Sub Method()
    Module1.Foo = 42
    Debug.Print Module1.Foo
End Sub
 
D'oh. I just closed the SE notifications. There was a question titled "Enumerating VBScript from Python", but I closed it and now I can't find the question.
Anybody still got the link visible?
 
I don't - chat got glitchy there for a bit so I closed it.
 
No, and I can't find it in SO search either.
@ThunderFrame It might be this: stackoverflow.com/questions/38361949/…
That's the closest one in name to your title that I can find in the new VBA questions.
It doesn't have an edit, but there is a chance it was changed by the author in the grace period.
 
@ThunderFrame Same one.
And no, I wasn't looking that whole time.
 
maybe I just saw it as "Enumerating" while glimpsing
 
[Hosch250/Rubberduck] Hosch250 pushed commit 4eab52df to inspectionBugs: Tests for ignored inspections and ignore quick fix. A few bug fixes.
 
TBH - Enumerating VBScript with Python would have been a much more interesting question...
 
> Showing 44 changed files with 2,405 additions and 148 deletions.
 
9:56 PM
Merge pull request #2049 from Hosch250/Issue2048

Fix crash in CE import command
[Hosch250/Rubberduck] web-flow pushed commit 196d5e73 to inspectionBugs: Merge branch 'next' into inspectionBugs
[Hosch250/Rubberduck] build for commit 4eab52df on inspectionBugs: AppVeyor build succeeded
 
@Comintern OLEView has errors when inspecting the Access TLB. PE Explorer doesn't seem to crash, but nor does it seem to have as much detail as what OLEView normally has.
 
@ThunderFrame Try OLEWoo.
 
[Hosch250/Rubberduck] build for commit 196d5e73 on inspectionBugs: AppVeyor build failed
BUILD FAILURE!
 
oh, that's a real application? I always thought that was a playful name for OLEView :-/
 
OK, honey, I'm right on it.
 
00:00 - 22:0022:00 - 00:00

« first day (768 days earlier)      last day (2412 days later) »