hmm, I think it's VBE throwing that error. If I have a project that opened with those errors, then attempting to add a module throws the same error (and the module is not added)
But I can add a new workbook, and add modules to that. i.e. the state of the project that opens with errors is permanently impaired in the VBE.
given my hit-rate on recent enhancement issues, I'm going to float this one here first ;-)... What if RD supported some annotations like @PredeclaredClass, @DefaultMember, @EnumMember, @ShortcuttedMember, @MemberHasDescription, and/or @MemberHasAttribute.
That would help identify when attributes are inadvertently lost, but also help with inspections? RD could have inspections like "Expected ClassX to be pre-declared, but attribute is missing or removed", or "Class X default member attribute is missing or removed", and the quickfix could apply or reinstate the attribute.
'@TestMethod
Public Sub TestMethod1() 'TODO Rename test
On Error GoTo TestFail
Dim first() As Variant
Dim second() As Variant
first = Sheet1.Range("A1:D3").Value
second = Sheet1.Range("A1:D3").Value
Assert.SequenceEquals first, second
TestExit:
Exit Sub
TestFail:
Assert.Fail "Test raised an error: #" & Err.Number & " - " & Err.Description
End Sub
Works with arbitrary number of dimensions and also tests equity of the LBounds and UBounds.
^ Could we perhaps change the location text to either include the name of the procedure (if it's a proc-level variable), or omit the procedure name if it's a module-level variable?
Do yourself a favor and use an ISO-8601 date format "YYYYMMDD" in your file names. That way your file names will sort in alphabetical and chronological order. — ThunderFrame1 min ago
♫ Imagine there's no date ambiguity, it's easy if you try ♫
given my hit-rate on recent enhancement issues, I'm going to float this one here first ;-)... What if RD supported some annotations like @PredeclaredClass, @DefaultMember, @EnumMember, @ShortcuttedMember, @MemberHasDescription, and/or @MemberHasAttribute.
And if we're think ahead to RD 3.0 - we could have intellisense for annotations, so just typing '@VB_A would be enough to get intellisense for the attribute annotations.
@ThunderFrame heck, you type @ and it lists the available annotations
gosh, SO
Sounds great. Except it's not a question. Stack Overflow is a Q&A site, not a "I need XYZ please do everything for me so I can paste it into my code and walk away happy without even trying" site. Please read How to Ask. — Mat's Mug21 secs ago
yep, but maybe annotations need "classes"... Eg. Type @, get a list of "Folder", "Inspection", "VB_Atrribute", then choose one, get the "members" for that "class"? Final annotation would look like '@Inspection.IgnoreVariableNotUsed True
@ThunderFrame If we deprecate the old annotation format, I'd recommend that we still support it with an added DeprecatedAnnotationInspection that has a quickfix to reformat them.
Neither the C code or the VBA code is allocating any memory. You're passing a pointer to a null string from VBA and then immediately passing that to sprintf. Your "program halt" is most likely a segfault. Either the C function needs to provide a buffer (an a way for the caller to release it) or it needs to be able to communicate how large of a buffer the caller needs to create. If you're attached to the interface, consider using snprintf and have the VBA code pass the buffer length instead. — Comintern35 secs ago
Pro tip. Don't try to call a C dll that you wrote with VBA code that you wrote if you don't understand either language.
@Comintern Do I recall correctly from way back in this chat that the VBE loads projects with an internal name and then renames them? If that is the case, our handler for the project load event might be interfering with the project load.
I guess that never happened before because, without the delay, we have been fast enough to not get in the way.
I've written a script to calculate the density of humid air at a given temperature and relative humidity, as these inputs are typically known for specific geographic locations. At the moment, the inputs are added into the code and the result is just printed to the immediate window.
The equation...
> Some inspections are module level, but others are specific to members of a module. Inspection Results' Location column should be more specific about the location by including the location's member name where appropriate.
> With new annotations for VB_Attributes, the number of annotations is growing. It can be hard to remember their names. In RD 3.0 we could have Intellisense for annotations, so it makes sense to think about categorizing annotations and also preparing for Intellisense.
I just installed .13 and noticed that there were 4 'Rubberduck install' (don't recall the exact name) processes in task manager. They did all end when the install finished - is this to be expected?
Can't say there never was before, this is the first time I've noticed.
> Per linked issue, this will be implemented as annotations:
'@ModuleAttribute.VB_Description("This module is responsible for XYZ") '@MemberAttribute.VB_Description("This procedure is responsible for XYZ")
Or:
'@Description("This module is responsible for XYZ")
The `@Description` annotation would be context-sensitive and become a module attribute when found in the declarations section, or a member attribute when found in a procedure.
> *RD could have inspections like "Expected ClassX to be pre-declared, but attribute is missing or removed", or "Class X default member attribute is missing or removed", and the quickfix could apply or reinstate the attribute*
I think it would be the other way around:
> **Missing Annotation** Procedure 'DoSomething' has member attribute '`VB_Description`', but no corresponding `@Description` annotation. Consider making module and member attributes expl
Can you please add some punctuation and capitalization? I started an edit but can't really tell where one thought starts and another ends in that 93 word run-on sentence at the start. — Comintern11 secs ago
WTH? You have 2 shift keys and a full spectrum of punctuation keys. They're there for a reason.
> Can't repro. How does that even happen? The current selection has (supposedly) no bearing whatsoever on the actual insertion point, which is [module.CountOfLines](github.com/rubberduck-vba/Rubberduck/blob/next/RetailCoder.VBE/UI/Command/AddTestMethodCommand.cs).
@Comintern looking at the code, I don't even see how it's possible
^ that. CreateObject takes a progId string literal. But if you're trying to figure out how a dictionary works, why not start with early binding so you get IntelliSense? Tools > References > Microsoft Scripting Runtime - that said I don't think anyone has a different version of that library unless they're running Windows < 98, so there's no need to use late-binding for it - the same version is on every single Windows box ever manufactured in this century. — Mat's Mug7 secs ago
@IvenBach look that the logs before you restart though
if there's an EXCEL.EXE ghost process running/lingering, tests can't run
2017-03-02 13:09:25.7366;ERROR-2.0.12.19847;Rubberduck.UI.Command.RunAllTestsCommand;System.Runtime.InteropServices.COMException (0x800A03EC): Cannot run the macro ''test.xlsm'!VBAProject.TestModule1.ModuleInitialize'. The macro may not be available in this workbook or all macros may be disabled.
I'm now getting a Sorry, we couldn't find '<file location>\<file name>.xlsm - [<Module name> (. Is it possible it was moved, renamed or deleted?' messagebox. What makes it odd is that the module name has a space at the end with a left parenthesis.
> The grammar doesn't enforce maximum identifier lengths (see #2855), yet we assume that no parser error means the code is compilable.
We need an error-level inspection result to pop for every identifier name that's longer than 255 characters - longer than 31 if it's a module name.
> **Identifier name is too long.** VBA will not compile code that contains identifiers longer than 255 characters, or module names longer than 31 characters.
Quickfix is obviously to run a *rename* refactorin
This answer is wrong/misleading. CreateObject creates a late-bound object, i.e. you don't need a reference to "Microsoft Scripting Runtime" - if you do reference the library, then using CreateObject is plain silly (for lack of a more expressive word); you can just do New Scripting.Dictionary and get IntelliSense and the runtime performance benefits of early binding. CreateObject takes a ProgId string literal, so that's CreateObject("Scripting.Dictionary"). — Mat's Mug1 min ago
It's not "accessing" the property - that operator is purely a compiler mechanism to inject the "name" of the argument into the code. In this case it will replace nameof(TestClass.Name) with "Name". The fact that it's non-static is irrelevant.
> That operator is purely a compiler mechanism to inject the "name" of the argument into the code.
with RD's COM API you can iterate, say, all enum members of a given enum in your code, and generate a dictionary keyed with enum values and returning the corresponding name - and then you can call that dictionary NameOf and do Debug.Print(NameOf(MyEnumValue)) to print "MyEnumValue"
I've seen many people use the following code:
Type t = typeof(obj1);
if (t == typeof(int))
// Some code here
But I know you could also do this:
if (obj1.GetType() == typeof(int))
// Some code here
Or this:
if (obj1 is int)
// Some code here
Personally, I feel the last one is ...
I've written a script to calculate the density of humid air at a given temperature and relative humidity, as these inputs are typically known for specific geographic locations. At the moment, the inputs are added into the code and the result is just printed to the immediate window.
The equation...
I just tested it - it's 255 characters...
It's not "accessing" the property - that operator is purely a compiler mechanism to inject the "name" of the argument into the code. In this case it will replace nameof(TestClass.Name) with "Name". The fact that it's non-static is irrelevant.
I've seen many people use the following code:
Type t = typeof(obj1);
if (t == typeof(int))
// Some code here
But I know you could also do this:
if (obj1.GetType() == typeof(int))
// Some code here
Or this:
if (obj1 is int)
// Some code here
Personally, I feel the last one is ...
VBA Rubberducking
VBA Rubberducking