« first day (388 days earlier)      last day (2792 days later) » 
00:00 - 04:0004:00 - 22:00

12:01 AM
RELOAD!
[Cardshifter/Cardshifter] 1 commit. 7 additions. 4 deletions.
[ckuhn203/Rubberduck] 9 commits. 910 additions. 179 deletions.
[Hosch250/Rubberduck] 29 commits. 7221 additions. 6413 deletions.
[rubberduck-vba/Rubberduck] 11 commits. 4 opened issues. 2 closed issues. 1 issue comment. 2722 additions. 2072 deletions.
[Vogel612/TranslationHelper\‌​] 3 commits. 2 closed issues. 122 additions. 18 deletions.
 
@Hosch250 well is it Class1 or Class8?
 
12:23 AM
Funny though, that I have a project involving interfaces each with 10 implementations, a List class used in countless places, that this project would crash the previous resolver code and work 100% as expected with the rewritten one, ....while cls7.Foo resolves to some unrelated member in an unrelated class...
 
12:36 AM
@Hosch250 make that 18 ;-)
 
12:49 AM
@Hosch250 ok I have a repro.
two things. one, I need to refine the reference resolution for events.
and two, ...I need to fix that shit.
 
@Duga Lol, I had about 3 commits and the rest are pulled from Mat and Duck.
 
I also have a repro on the non-resolution of Class5.Name from references in Class6
 
OK, thanks.
 
loading up project in VS
damn my laptop is slow
 
1:14 AM
launching fix1 - events should only be resolvable to local scope
building
loading hoschbug.xlsm
fail
ok I need a listener override for RaiseEvent
uh, there's already one
wtf is going on here
 
The bloody thing fucking works!
 
[ckuhn203/Rubberduck] ckuhn203 pushed commit b16d6e7d to sourcecontrol: closes #667; Git integration is a shippable beta
2
 
@RubberDuck awesome!!
I'm still working on frakkin resolution code...
 
[rubberduck-vba/Rubberduck] build for commit b16d6e7d on ???: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit b16d6e7d on ???: AppVeyor build succeeded
 
I'll be away for a while now. Need to get away from my laptop for a day or two.
 
1:28 AM
cool
the event gets picked up by FindProjectScopeDeclaration, which assumes anything Public is possibly in a "static" class.
we'll need to figure out a way to get the resolver to know about class attributes one way or another
 
@RubberDuck PR it first!
 
@Hosch250 PR is there, but it's been such a marathon I'm not ready to review it.
 
OK.
 
So, by all means, review, pull it, let it sit..... I don't care.
It works.
I need a break. lol
 
1:31 AM
I know the feeling.
 
well earned Chris, well earned :)
 
I took my break by writing the translation helper.
 
lol
event resolution is fixed
    private Declaration FindProjectScopeDeclaration(string identifierName)
    {
        var matches = _declarations[identifierName];
        try
        {
            return matches.SingleOrDefault(item =>
                !item.DeclarationType.HasFlag(DeclarationType.Member)
                && item.DeclarationType != DeclarationType.Event // events can't be called outside the class they're declared in
                && (item.Accessibility == Accessibility.Public
                    || item.Accessibility == Accessibility.Global
 
I don't know what you are doing here, but good job.
 
one down
 
1:34 AM
@rubberduckvba #Git integrated into the #VBA editor? Nonsense you say? No. It's real. Powered by @libgit2sharp https://github.com/rubberduck-vba/Rubberduck/pull/669
 
@RubberDuck That was for @Mat'sMug, but have a retweet (once I log in).
 
@Hosch250
    callee = FindLocalScopeDeclaration(identifierName, localScope)
                ?? FindModuleScopeProcedure(identifierName, localScope, accessorType, isAssignmentTarget)
                ?? FindModuleScopeDeclaration(identifierName, localScope)
                ?? FindProjectScopeDeclaration(identifierName);
identifiers are resolved in a sequence
the Foo event was picked up at the last step FindProjectScopeDeclaration
 
OK.
 
because I hadn't explicitly excluded DeclarationType.Event from that method
it's basically picking up anything that's not a member - the intention was to pick up global variables, constants, enums, UDT's... but not events.
now there may be issues with that method still, because the resolver doesn't know if a class has a default instance or not, which makes a difference in how members are allowed to be accessed.
 
Yikes, sounds awful.
 
1:41 AM
that flag is set in the module attributes, you have to export the class, edit it in notepad, and re-import it to make it happen
 
Awful.
 
my List class has such an attribute, so you can call List.Create("foo", "bar") legally
 
@Rubberduck203 @libgit2sharp I'm putting the final touches on the resolver, and it's shipping. Like, very, very soon. #NextReleaseRocks
 
without the flag you need a Dim lst As New List declaration, to call it at instance level, like, uh... Set lst = lst.Create("foo", "bar") ...well that makes no sense, but you get the idea ;-)
so, moving on to that parameterized property shit
gets picked up as a member call as expected
c gets picked up correctly
(as Class5)
accessor is ContextAccessorType.AssignValue as expected, isTarget is True as expected
(that means resolver knows to look for Property Let)
oh wow
 
A bug? A feature?
 
1:54 AM
it's passing c for localScope to ResolveInternal(VBAParser.ICS_S_ProcedureOrArrayCallContext
should pass Class5
it worked in With blocks because the _withBlockQualifiers stack is storing the type of the qualifier
building
and fixed
now the only known issue left is that darn caching problem
@Hosch250 you just saved the freakin' day with that bug
 
Nice.
 
works perfectly
oh shit
I'm on [next]
damn
 
You mean RD next?
 
yes
well, too fucking bad
 
If it works...
 
2:03 AM
[rubberduck-vba/Rubberduck] retailcoder pushed commit 2c03f0a4 to next: removed redundant ResolveIdentifier method; project-scope declarations now exclude event declarations, and member calls outside With blocks now resolve correctly.
[rubberduck-vba/Rubberduck] build for commit 9ea3f5dc on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 9ea3f5dc on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 9ea3f5dc on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 9ea3f5dc on next: AppVeyor build succeeded
 
@Hosch250 I'm really scared to merge #661
 
661? Is that mine?
 
Yeah, that's mine.
 
+6,773 −6,612
 
2:05 AM
Fork my repo and check it out.
@Mat'sMug That's not my changes!
 
Commits 182 Files changed 148
 
Those are your changes!
 
I know, but finding your changes is ...hard.
 
Every time I pull, Git puts the changes in my next push.
Here, I'll show you the new ones.
Wait, don't merge.
Something funny happened with one of them that I need to look into better.
Check this out:
And that.
 
[rubberduck-vba/Rubberduck] ckuhn203 pushed commit 636b9657 to next: fixes #668
[rubberduck-vba/Rubberduck] ckuhn203 pushed commit fa4de1be to next: added xlsx to gitignore
[rubberduck-vba/Rubberduck] ckuhn203 pushed commit 41bc9b43 to next: Fixed display of commits
[rubberduck-vba/Rubberduck] ckuhn203 pushed commit 55232653 to next: extracted secondary panel concept to allow for #667
[rubberduck-vba/Rubberduck] ckuhn203 pushed commit b16d6e7d to next: closes #667; Git integration is a shippable beta
Merge pull request #669 from ckuhn203/sourcecontrol

Sourcecontrol - Beta ready
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
 
2:14 AM
There's the fix.
 
[Hosch250/Rubberduck] Hosch250 pushed commit 76990d2b to next: Fix regex rename
[rubberduck-vba/Rubberduck] build for commit 76990d2b on ???: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 76990d2b on ???: AppVeyor build succeeded
 
So, @Mat'sMug, this is the case:
First, I copy/pasted some of my changes from GrammarIsFun (local fork), and committed: github.com/Hosch250/Rubberduck/commit/…
I just realized that I already had committed my changes, and just needed to uncomment, so I copy/pasted from the current Next, and redid everything I'd undone: github.com/Hosch250/Rubberduck/commit/…
 
Wait a sec - don't merge yet.
 
[Hosch250/Rubberduck] ckuhn203 pushed commit fa4de1be to next: added xlsx to gitignore
[Hosch250/Rubberduck] ckuhn203 pushed commit 41bc9b43 to next: Fixed display of commits
[Hosch250/Rubberduck] ckuhn203 pushed commit 55232653 to next: extracted secondary panel concept to allow for #667
[Hosch250/Rubberduck] ckuhn203 pushed commit b16d6e7d to next: closes #667; Git integration is a shippable beta
[Hosch250/Rubberduck] retailcoder pushed commit 2c03f0a4 to next: removed redundant ResolveIdentifier method; project-scope declarations now exclude event declarations, and member calls outside With blocks now resolve correctly.
 
2:18 AM
Now I need to remove a parameter.
 
Merge pull request #669 from ckuhn203/sourcecontrol

Sourcecontrol - Beta ready
Merge pull request #6 from rubberduck-vba/next

Pull Next
[rubberduck-vba/Rubberduck] build for commit 13625317 on ???: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 13625317 on ???: AppVeyor build succeeded
 
It works!
 
what does?
 
The resolution and renaming.
The only trouble is, you broke Reorder and Remove.
 
how so?
 
2:23 AM
Sub Main()

    Dim c As New Class5

    c.Name("John", "M") = "Smith"

    Debug.Print c.Name("John", "M")

End Sub
 
That works perfectly for rename.
But when you do reorder:
Sub Main()

    Dim c As New Class5

    c.Test("John", "M") = "Smith"

    Debug.Print c.Test("M", "John")

End Sub
 
yeah I saw
 
Also, find all references doesn't find any others for that first one.
 
and it shouldn't
references to a Property Let are not references to a Property Get
 
2:25 AM
I know.
I need to fix that.
Dishes time now, but will do tomorrow first thing.
 
it's an edge case, fix it for 1.4.1
 
OK.
 
can I merge the PR?
 
But, I don't like my code to have bugs :(
Yes.
 
2:27 AM
We are down to 114 issues.
And 0 PR's.
 
sync'd, building.
 
BBL.
Let me know if it fixes the issue.
 
A VBA Coding Manifesto (Part 1) http://wp.me/p3bqG4-fp via @Option_Explicit
 
I left the regex line in, but commented out for now.
 
[rubberduck-vba/Rubberduck] build for commit 0ca25aff on sourcecontrol: AppVeyor build succeeded
 
2:28 AM
:22440521
    Bar .Renamed.Renamed
 
[rubberduck-vba/Rubberduck] build for commit 0ca25aff on sourcecontrol: AppVeyor build succeeded
 
doesn't work??
 
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
 
        private string GetReplacementLine(string content, string target, string newName, Selection selection)
        {
            // until we figure out how to replace actual tokens,
            // this is going to have to be done the ugly way...

            // todo: come back after the identifier references are fixed
            //var contentWithoutOldName = content.Remove(selection.StartColumn - 1, selection.EndColumn - selection.StartColumn);
            //return contentWithoutOldName.Insert(selection.StartColumn - 1, newName);
it's still a regex replace??
dude, wtf?
oh
5 mins ago, by Hosch250
I left the regex line in, but commented out for now.
commented-out meaning, the fix is commented-out!
 
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit ee10f36a on next: AppVeyor build succeeded
 
2:35 AM
IT WORKS!!
        Bar .Foo.Fuzz
 
@Mat'sMug Don't you love ambiguity in language? :P
 
lol
 
[rubberduck-vba/Rubberduck] retailcoder pushed commit a2b52c89 to next: replaced regex-rename with selection-based surgical replacements.
[rubberduck-vba/Rubberduck] build for commit a2b52c89 on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit a2b52c89 on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] retailcoder pushed commit 6b0c56a3 to next: removed unused InterfaceImplementationListener and commented-out deadcode in VBProjectParseResult
[rubberduck-vba/Rubberduck] build for commit 6b0c56a3 on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 6b0c56a3 on next: AppVeyor build succeeded
 
ok. switching to release config
release build started
 
[rubberduck-vba/Rubberduck] build for commit 6b0c56a3 on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 6b0c56a3 on next: AppVeyor build succeeded
 
2:43 AM
uh, why isn't the Source Control menu doing anything?
dammit
this better be a just on my machine problem
installer created
I'm going to have a cigarette, then I'm booting my work laptop and running the 1.4 installer.
@Rossco what's your confidence level? ;-)
 
3:09 AM
install completed
launching Excel
drumroll
it works!
and I just found another issue with the resolver
ElseIf Not Framework.Strings.Contains(procedure, "'!") Then
"Framework" is a standard module, "Strings" is a public variable in that module
resolver doesn't pick it up
 
3:30 AM
@Mat'sMug That's weird, I know I uncommented the other lines before my last commit.
Does it work?
 
the rename, yes
I need to switch back to debug build and fix that resolver issue
 
Reorder bug fixed.
I need to see if interfaces/events are affected too.
Events fine.
Interfaces fine.
 
cool. PR!
 
@Mat'sMug No wonder!
 
[Hosch250/Rubberduck] Hosch250 pushed commit df501aef to next: Finish fixing regex rename
[Hosch250/Rubberduck] Hosch250 pushed commit feddd22b to next: Fix reorder params getter/letter/setter bug.
 
3:37 AM
I'd never synced that commit!
There might be a conflict now.
@Mat'sMug Hold on - it's a two line copy/paste fix to get Remove done too.
 
NP
 
[Hosch250/Rubberduck] Hosch250 pushed commit 23a5a4b4 to next: Fix remove params getter/letter/setter bug
 
Yup, there's a merge conflict.
 
[Hosch250/Rubberduck] retailcoder pushed commit a2b52c89 to next: replaced regex-rename with selection-based surgical replacements.
[Hosch250/Rubberduck] retailcoder pushed commit 6b0c56a3 to next: removed unused InterfaceImplementationListener and commented-out deadcode in VBProjectParseResult
[Hosch250/Rubberduck] Hosch250 pushed commit 68c2b0e6 to next: Pull and fix merge conflict
 
@Mat'sMug PR'ed, waiting for results.
 
3:44 AM
I can't repro the resolver bug on a small-scale project
 
[rubberduck-vba/Rubberduck] build for commit 68c2b0e6 on ???: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit 68c2b0e6 on ???: AppVeyor build succeeded
 
oh..
hold on
 
I now removed the regex line and the comments around it.
 
did you sync before doing that?
I had them removed already
 
I fixed the merge conflict on my system by pulling before PR'ing.
 
3:47 AM
ok
 
I committed and forgot to sync.
Then you committed, and I had to pull and resolve the conflicts.
 
@Mat'sMug Retrospectively, my confidence is pretty high.
 
lol
 
Umm, do you guys know that the rubberduck website is pointing to v1.22 as the latest version?
 
Yeah, we are just in the process of releasing now.
After @Mat'sMug merges my PR, that is.
 
3:51 AM
I thought 1.3 was latest? Because aren't you pushing for 1.4 now?
 
Oh, pre release.
 
^^
1.3 was borked
 
np, I was just checking whether you had released yet or not.
 
3:52 AM
I haven't been following the chatter closely today.
 
no, still trying to repro a bug I have with a project I loaded up on the machine I'm using to test before releasing
 
Lines 375-381 on that last one in the RenamePresenter file only.
 
@Hosch250 that one probably conflicted
 
Yep.
That's the one where I had to manually fix the conflicts on the lines mentioned.
 
3:54 AM
merged
 
[rubberduck-vba/Rubberduck] Hosch250 pushed commit df501aef to next: Finish fixing regex rename
[rubberduck-vba/Rubberduck] Hosch250 pushed commit feddd22b to next: Fix reorder params getter/letter/setter bug.
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 23a5a4b4 to next: Fix remove params getter/letter/setter bug
[rubberduck-vba/Rubberduck] Hosch250 pushed commit 68c2b0e6 to next: Pull and fix merge conflict
Merge pull request #670 from Hosch250/next

Fix bugs in reorder/remove params
[rubberduck-vba/Rubberduck] build for commit b0e1f41f on next: AppVeyor build succeeded
[rubberduck-vba/Rubberduck] build for commit b0e1f41f on next: AppVeyor build succeeded
 
and I got the repro
if a public field's name is conflicting with a module from the VBA standard library, shit hits the fan
so Framework.Strings blows up because resolver can't decide between VBAProject1.Framework.Strings and VBA.Strings
 
Makes a lot of sense.
 
yeah, except it's legal and should be handled properly.
the standard lib declarations should be RD's "last resort" for finding references
 
Will it be a hard fix, or not really?
 
3:59 AM
crazy hard
 
Ouch.
 
return matches.SingleOrDefault(item => !item.IsBuiltIn &&
...
lol
fixed in 3... 2... 1...
 
00:00 - 04:0004:00 - 22:00

« first day (388 days earlier)      last day (2792 days later) »