VBA Rubberducking

Mathieu Guindon

9:00 PM

a let assignment isn't really suspicious if RHS isn't an object, no?

23fc9a62-56de-47fb-97b4-737890

There's two problems you'd have to consider here.

M.Doerner

A separate inspection has the advantage that ObjectVariableRequiresSet can stay as Error serverity.

Mathieu Guindon

we definitely want that

23fc9a62-56de-47fb-97b4-737890

#1 is that each call takes 2 arguments. You'd have to pull that into a single type instance or something, then append N values of that data set.

IvenBach

I'm thinking of using a value tuple but have to remember how to properly do that.

M.Doerner

9:01 PM

I just recalled, the ImplicitDefaultMemberAssignment will not fire, if Let is used.

23fc9a62-56de-47fb-97b4-737890

#2 is that they aren't necessarily the same call. AppendStream followed by AppendString repeatedly wouldn't necessarily be improved--although it would be possible.

@IvenBach I'd create a new struct.

Also, I'd put the type on it as well. Instead of AppendStream, just make it Append(new Foo { Format, Type, Value })

IvenBach

I don't quite follow you on that.

Mathieu Guindon

@M.Doerner wait so Range("A1") = 42 doesn't fire anything?

doesn't feel right

M.Doerner

No, Let Range("A1") = 42 does not fire anything.

Mathieu Guindon

wut lol

M.Doerner

9:04 PM

Range("A1") = 42 will

Mathieu Guindon

by design or by accident?

M.Doerner

It has been implemented like that before and there are even tests for this behaviour.

this

I would assert that this is not what we want

Mathieu Guindon

and I bet I'm in the git blame for that... sigh

this

while the Let means that it can't be Set-coereced, we still have code that doesn't do what it say.

Mathieu Guindon

9:05 PM

^

M.Doerner

The old implementation actually looked at the letContext to see whether a LET was present.

this

(or rather isn't very clear in saying what it does)

consider also the case where a strange object has default property that is not Value

M.Doerner

I can change that, if you wnat.

Mathieu Guindon

yes please! :)

M.Doerner

It will just recurse in the resolution.

this

9:06 PM

which makes me think-- do we want everyoen to start using Range("A1").[_Default] = 42?

Vogel612

@this no? We want them to use ws.Range("A1").Value = 42

this

I think everyone would recoil in horror to that.

M.Doerner

A quickfix will noot really have any other chance then using that.

Mathieu Guindon

@this no - we'll make the inspection info mention that sometimes the default member may not be the member you want

this

^

@Vogel612 yes that's actually what we want (or maybe Value2). But neither are the default which quickfix can only do.

Mathieu Guindon

9:08 PM

the xml-doc can go in more details about it

this

An idea, though is that we can further check if a member is hidden & bracketed (or maybe just or'd) to add a TODO change the default member

Mathieu Guindon

meh

this

to make users change it to Value or Value2 manually

Mathieu Guindon

if it's parameterized, they want Item

this

I think Excel is the only one to have this WTFworthy behavior of using a hidden & bracketed member as its default member.

Mathieu Guindon

9:10 PM

but Range isn't the only WTF in its type lib :)

that said if that's the case, and given Excel is probably our host ~90% of the time, it could be worth having some Excel-specific logic in there

hmm, could we have an Excel-specific quickfix?

like, if the host is Excel and we're looking at a Range, some MakeRangeImplicitDefaultMemberCallExplicitQuickFix could look at how the member call is parameterized, and yield a call to Value or Item accordingly?

wait no, not the host - the library

Duga

[rubberduck-vba/Rubberduck] Vogel612 added label feature-code-explorer to issue #5098: Public enum value is not updated in CE after a parse

Mathieu Guindon

@Duga #ShouldIBlameCaching.com

Vogel612

@MathieuGuindon yea, that's the relevant part.

Duga

[rubberduck-vba/Rubberduck] MDoerner created comment on issue #4281: Inspection for suspicious implicit conversion in specific syntax nodes

> Please note that according to the specification all three expressions in For i = <expr1> To <expr2> Step <expr3> are coerced to Double, not to Long.

IvenBach

@23fc9a62-56de-47fb-97b4-737890 Structs can't be null?

23fc9a62-56de-47fb-97b4-737890

9:14 PM

@IvenBach Today you learn :)

That's right.

IvenBach

:derp: it's a value type so that's a nope.

What IF I don't provide that info?

Mathieu Guindon

and if Excel lib isn't referenced, then we don't list the Excel-specific quickfix

IOW the inspection doesn't have to care for Excel-specifics, just the quickfix

IvenBach

A struct is to C# as a UDT is to VBA.

Mathieu Guindon

@Duga nice catch!

@IvenBach exactly!

Vogel612

is it, though?

IvenBach

9:16 PM

Not 100% exactly.

Vogel612

I doubt that UDTs are allowed to be stored on the stack...

Mathieu Guindon

aye, you can't pass them around without cursing

IvenBach

But cough I'm using it loosey goosey hand-wavey right now.

Mathieu Guindon

@IvenBach exactly!

IvenBach

Mkay... I've created the struct now how do I instantiate one? Ignore my terribly incorrect terminology right now.

23fc9a62-56de-47fb-97b4-737890

9:18 PM

@IvenBach new.

Just like a class.

Duga

[rubberduck-vba/Rubberduck] MDoerner opened issue #5099: Suspicious Let assignment inspection

> **What**
The inspection should find let assignments that require default member accesses on both sides of the assignment.

**Why**
It is not unlikely that such an assignment is an error and the actual intention was to use a Set assignment between the objects.

**Example**
This code should trigger the inspection:

```vb
Public Sub DoSomething()
Dim target As Excel.Range
Dim source As Excel.Range
target = source
End Sub
```

---

**QuickFixes**

1. **AddSetQuick

[rubberduck-vba/Rubberduck] MDoerner added label enhancement to issue #5099: Suspicious Let assignment inspection

[rubberduck-vba/Rubberduck] MDoerner added label feature-inspections to issue #5099: Suspicious Let assignment inspection

[rubberduck-vba/Rubberduck] MDoerner assigned MDoerner to issue #5099: Suspicious Let assignment inspection

IvenBach

@23fc9a62-56de-47fb-97b4-737890 It's my questions like these that make me feel inadequate...

Duga

[rubberduck-vba/Rubberduck] MDoerner added label up-for-grabs to issue #5099: Suspicious Let assignment inspection

23fc9a62-56de-47fb-97b4-737890

LOL.

I know the feeling.

Mathieu Guindon

@Duga question: should that inspection ignore LetStmtContext that have an actual explicit LET token?

23fc9a62-56de-47fb-97b4-737890

9:20 PM

I mean, I learned what a REST API was just the other day.

It's an HTML POST/PUT/GET/DELETE call...

Mathieu Guindon

meh. let's not give our users a reason to use Let

this

@MathieuGuindon IMO, no because while it's not Set, it's still implicit.

Ducky should be saying "say nope to dope, ugh to drugs, and explicit No to implicit" to the users.

Mathieu Guindon

but if I explicitly write Let target = source, clearly my intent isn't to Set something

this

(Ok I dropped the ball there with the rhyming but you get the idea)

Obviously not but why be implicit about what member are you accessing?

Don't forget that it can be chained, too.

Mathieu Guindon

@this aye, and that's ImplicitDefaultMemberAssignment's job to flag it, no?

(and will still flag it regardless)

this

9:23 PM

Let dumb = dumber => Let dumb = dumber.Dumbest.DumbestOfThemAll

hmm. I guess you're right.

M.Doerner

OK, I can see that we should exclude the ones with explicit Let.

this

for the proposed supsicious inspection, yes.

Mathieu Guindon

also, wouldn't making the LHS & RHS implicit calls explicit be a valid fix?

M.Doerner

BTW, I found another situation where this is really hideous, when assigning function return values.

However, there it will most likely trigger the FunctionReturnValueNotSetInspection.

Mathieu Guindon

we're starting to have quite a lot of pretty nifty inspections :glee:

IvenBach

9:28 PM

@23fc9a62-56de-47fb-97b4-737890 Then I'm in good company. My WTF-is-this-face is thoroughly being used right now.

Vogel612

@23fc9a62-56de-47fb-97b4-737890 there's also HEAD and OPTIONS and the http 1.1 standard allows arbitrary verbs, though the server is not required to support them

23fc9a62-56de-47fb-97b4-737890

@Vogel612 Yep.

That's the advanced stuff, though :)

Vogel612

for 99% of the cases you don't need HEAD or OPTIONS

23fc9a62-56de-47fb-97b4-737890

And PUT and POST are fairly similar.

Just PUT is idempotent, IIRC, and POST is not.

Vogel612

some REST APIs make a distinction on HEAD and GET for async requests, though

this

9:31 PM

I thought that HEAD is required to be implemented for all GETs....

Mathieu Guindon

some REST APIs use PUT to GET stuff, and they need to burn.

23fc9a62-56de-47fb-97b4-737890

GET and POST can handle everything else though.

Vogel612

@this most servers just forward it to GET

M.Doerner

PUT to get stuff is strange.

Mathieu Guindon

very

this

9:31 PM

^

Vogel612

@MathieuGuindon ~grabs flamethrower

this

@Vogel612 I see. IINM, they do correctly return empty bodies, even though using GET would have had bodies.

M.Doerner

Isn't is supposed to be GET -> get, POST -> create, PUT -> update, DELETE -> delete?

23fc9a62-56de-47fb-97b4-737890

I can go back to Hosch250 on Saturday!

M.Doerner

At least for storage.

23fc9a62-56de-47fb-97b4-737890

9:33 PM

I'm getting a little tired of being 23f.

Mathieu Guindon

@M.Doerner in theory, yes.

this

TBH, REST never really felt much of a standard anyway. Everyone never actually do it consistently

M.Doerner

And then people mess it up.

Mathieu Guindon

^

23fc9a62-56de-47fb-97b4-737890

Although it's hilarious getting comments about it. One person even pinged me on LinkedIn about it :D

Vogel612

9:33 PM

damn

Mathieu Guindon

haha

this

LOL

23fc9a62-56de-47fb-97b4-737890

Anyway, TTQW. See you tomorrow!

Mathieu Guindon

yeehaw ttqw here to

(that started as a typo with "yeah" rendered as "yeha" and I just rolled with it)

this

for me the biggest annoyance is that you have to still do a lot of reading to use someone's API because one API might like to use query parameters while other API wants everything in the body, while yet another might use a mixture. That doesn't feel like an improvement but hey, it's popular™!

M.Doerner

9:46 PM

@MathieuGuindon At least the following is not legal.

Private Sub TestSub()
    Dim target As Object
    target = New Excel.Application
End Sub

this

Makes sense, the New keyword basically prevents the let assignment.

M.Doerner

No default member access on newStatemets.

this

we get no such thing with CreateObject/GetObject/equivalents, though.

M.Doerner

That is because they are functions and not statements.

Mathieu Guindon

@M.Doerner phew!

now wrap RHS in parens, and I bet it befomes legit

M.Doerner

9:48 PM

I will have to enhance the inspection a bit to recognize that, though.

No, it does not.

No default member coercion on newStatements.

Mathieu Guindon

Cool

M.Doerner

Well, I will double check.

I might have conflated two things here.

I hope not.

Oh darn, it is legal.

I conflated Let coercion with procedure coercion.

You cannot access procedure default members in call statements from freshly newed up objects.

BTW, that is one of the most stupid ways to assign the string Microsoft Excel.

this

to be honest, the whole business with the parentheses annoys me the most about VBA.

I don't know what Joel was smoking but he had to be smoking some hard stuff at that time

M.Doerner

The version without parentheses is also legal.

this

I'm confused. Are we talking about this? target = New Excel.Application

IvenBach

9:58 PM

So when you paste HTML info into excel it converts according to the <div> and other tags to be in the correct cells?

M.Doerner

Yes, that is legal. I just confused it with the procedure coercion.

this

yuck

Yes, @IvenBach probably a relic from the era when Microsoft was "you can HTML anything in Office!"

IvenBach

Hrm... And that builds on top of the UTF8 encoding or whichever it's encoded in, leading back to Joel's article.

KySoto

-_- no ones touched my question

looks like im screwed

that or im going to have to wait a couple months

Vogel612

that three hours old one on SO?

KySoto

10:11 PM

its already a couple pages in

but i also posted it on reddit and spice works

oh... it moves

cuz its on the first page now

this

10:24 PM

why are you doing it from powershell?

I'd consider just doing the actual work in SSIS or Access, and just use PowerShell to start either as opposed to doing the work in powershell.

mansellan

@23fc9a62-56de-47fb-97b4-737890 Nearly - it's an HTTP POST/PUT/GET/DELETE, and stateless. Using HTTP semantics as they were designed, rather than jamming huge globs of state data in a POST.

@this TBF, I don't think I've seen it claimed as a standard anywhere. Its more of an ethos iiuc.

related: I highly reccomend RestEase if you need to connect to REST endpoints from c#. Very elegant API.

this

I do recall some ppl waving their hand that it's not a standard or spec, whatever. But frankly it's not much if everyone and their dog can do anything they want

mansellan

(ymmv :-) )

this

10:39 PM

it's kind like "Ok, we'll just agree to use verbs and use it as what it say but how you want to do it, well, do whatever"

mansellan

@this Swagger. Just saying :-)

this

Yeah I know about them. It does help but still.

You can't implement someone's REST "API" without reading it through.

Contrast this to a nuget package or even a dumb ol' DLL.

yo, there be function here, you call it with so and so and it gives you this fo shizzle.

mansellan

Sure.... but given the choice between downloading some WSDL and (auto?)genning a proxy, versus loading a swagger page and hitting Execute, I know which I prefer :-)

this

with REST, it's all way back to C where we have to wrangle the calling convention, the stack location, and all mindless plumbing details BEFORE we get to actually using it.

mansellan

You still have the option of putting proxies in a NuGet, but nobody feels the need...

this

10:43 PM

Autogen might be nice thing to do but if something goes wrong, you better know what the hell is going underneath the stack. That is a main reason IMNSHO why WCF or SOAP failed

mansellan

well that, plus it's sooooo blooooated.

this

and I'm not talking about proxies to be clear. I get the desire to not have to deal with proxies at all. I'm totally down with that.

but do we really have to wrangle the calling convention?

Mathieu Guindon

pretty happy with RestEase tbh

mansellan

@this tbh, not really following... calling convention?

this

Ok let's start over.

In C you had to agree on a calling convention.

mansellan

10:45 PM

sorry! I'm probably being slow. Been a long day :-)

this

e.g. do you push the parameters on the stack? On the heap? in what order?

BBOOOOOOORRRRRRRIIIIIINNNNNNGGGGGGG

I just want to call the function!

mansellan

yep, vaguely aware that C had such issues

(Not knowing anything much about C)

this

and that is why people quickly decided that in higher level language to not bother with that plumbing details.

but now with REST API, we are back to wrangling the calling convention.

Why? Because we can choose between query string parameters, body

we also have to negotiate the content. JSON? XML? Form encoded? Some weird media type?

BBOOOOOOORRRRRRRIIIIIINNNNNNGGGGGGG

mansellan

Oh yes, I see...

mulls

this

That's why I think REST is a step back in that respect.

Do not get me wrong. I'd much rather use REST over WCF, SOAP, whatever

mansellan

10:47 PM

still mulling

this

and we have nuget packages that makes REST stuff easy, but there's no escaping the fact that I must read and understand how to call someone's API before I can actually use it.

and then you have those clowns who do a half-assed job of implementing their REST API like using POST for everything, or using GET to update something or what have you.

So in that respect, it's worse than C's calling convention situation because you can only have so many calling conventions, but with REST, the variations are limitless

mansellan

I guess I don't see it much, because with RestEase all that is abstracted into the client interface.... It's the API designer's job to define which params are query, body, form, the caller just hits a C# interface. Media types, not so much, you still need to know if you're getting XML or JSON for example - but you don't have to set headers explicitly.

Only really works in a work setting, where you know your callers are modern .net. On the open web, it wouldn't really work.

this

wait a minute. Keep in mind i haven't used RestEase, only RestSharp (been meaning to look into RestEase but hadn't need yet)

are you telling me that REstEase generates proxy?

mansellan

yes, dynamically with Reflection.Emit, from an attributed spec interface.

it's really quite nice.

this

oh ok that is nice

mansellan

10:53 PM

^ will generate a proxy at runtime

this

does it depend on having swagger?

mansellan

no, it knows nothing about the server at all, let alone swagger.

its a dynamic client proxy generator

it only knows what it's told in the client interface

this

sorry I'm confused.

so I still have to read some clown's API specs and write my proxy?

mansellan

think WCF proxies, but emitted at runtime, and using an attributed interface as its input rather than server-provided WSDL

this

Ok, so I still have to read the clown's API specs to write that interface

BBOOOOOOORRRRRRRIIIIIINNNNNNGGGGGGG

:D

mansellan

10:57 PM

@this Hopefully the clown wrote it for you and put it in a NuGet. That's what we do at work. Boring for the API clown, easy-street for the caller.

Like I say, not really an option on the open web.

(Unless you wanna write an interface for random-clown's API)

:-)

this

yeah - and that's my biggest beef with the REST. I love what they have done w/ Swagger, esp the standardization of docs page

but it still doesn't get away from the fact that I must negotiate the parameter placement, the content / media type and all that kind of crap

mansellan

TBF, I'm surprised nobody's come up with a way to use Swagger's json spec to do something like WSDL used to do...

this

in end all I want is function name, a bucket for my parameters, and a return value.

don't bother me with silly nitpicks about query string parameters, headers, body, and a bajillion other hiding places HTTP offers.

I think you can see that I'm quite lazy. :D

mansellan

In a closed environment, REST can be really very nice. Inject an interface, call as if local.

I take your point that on the web it might suck.

@this Don't knock laziness. Often it takes hard work to enable laziness.

3

this

^

mansellan

11:03 PM

I would say though that RestSharp is pretty low-level. You'd relieve at least some of the boredom using RestEase.

(or at least reduce your SLoC)

IvenBach

I think I need a breadcrumb with this refactoring.

Anyone available?

mansellan

@IvenBach uhm, I can try?

IvenBach

I'm working on refactoring the copy to clipboard command.

One sec I'm trying to clean it up a bit so I can push to a repo and link to it for a better example.

Vogel612

@mansellan ~sigh

"used to"?

also... you sure that's not the case?

After all in Java enterprise land, Swagger JSONs are generated from JAX-RS annotations

that's basically ready for WSDL Schema generation or any kind of dynamic type declaration shenanigans you can think of..

mansellan

11:19 PM

googles JAX-RS

hmm, with Swashbuckle it uses refection and XML docs to generate the spec JSON

not seen anything that can consume that to generate a .net client proxy though. perhaps there's something out there, but not found it.

@Vogel612 Yes, used to. Friends don't let friends SOAP :-)

Vogel612

yea, about that...

Duga

[rubberduck-vba/Rubberduck] IvenBach synchronized pull request #5095: Add description filter for Code Inspections

Vogel612

for work, I've needed to deal with manually crafted SOAP bodies

mansellan

Sorry, s/b "S"OAP :-)

Vogel612

passed through a stringly typed in memory message queueing system

mansellan

11:23 PM

ewww

Vogel612

yea it stopped working when I upgraded the MMQS dependency version

mansellan

You had my sympathy at "Java"...

Duga

[rubberduck-vba/Rubberduck] IvenBach synchronized pull request #5095: Add description filter for Code Inspections

Mathieu Guindon

@Vogel612 heads up, I just replied to a comment on WP linking here; guy has a question about VBA SDK and doesn't know where to ask, so he might pop in and require write access

Vogel612

I'll be around for around half an hour at least now

mansellan

11:27 PM

@MathieuGuindon WP?

Vogel612

wordpress

mansellan

ah ok

the blog

IvenBach

@mansellan github.com/rubberduck-vba/Rubberduck/pull/5095 has my changes. The last commit was consolidating the logic. I'm running into the problem of using IEnumerable<object> results which is coerced later into a 2D array that's then later use by ExportFormatter.

Duga

[rubberduck-vba/Rubberduck] build for commit f815e05c on unknown branch: AppVeyor build failed

BUILD FAILURE!

[rubberduck-vba/Rubberduck] MDoerner edited pull request #5089: Resolve recursive and parameterless default member accesses

mansellan

@IvenBach uhm, are you sure that's a 2D array? You have an IEnumerable<Object>, which you're calling Select(result => result.ToArray()) on.... Air coding here, but that means "take each object in the set, and turn it into an array"

If you set a breakpoint right after that line, does resultsAsArray look like you hope it would?

Duga

11:34 PM

[rubberduck-vba/Rubberduck] build for commit ab4ad177 on unknown branch: AppVeyor build failed

BUILD FAILURE!

IvenBach

About 75% of the time I can work with things without fully understanding whats going on with them. "'object' does not contain a definition for 'ToArray' and no accessible extension method 'ToArray' accepting a first argument of
type 'object' could be found" which makes sense.

mansellan

Yeah that's what I'd expect

IvenBach

I don't really want to use object but that's the least common denominator between them.

mansellan

each element of your IEnumerable<object> is an object. So your Select works on individual objects in the the set.

and object doesn't have a ToArray() method.

IvenBach

That much I can follow.

mansellan

11:37 PM

So, you're passing in an IEnumerable<object> ("some sequence of things"), and hoping to make it 2D. You don't have enough information at that point to do that.

Where are the boundaries between rows? How would it know?

IvenBach

For writing out the information? I don't quite follow.

Duga

[rubberduck-vba/Rubberduck] MDoerner synchronized pull request #5089: Resolve recursive and parameterless default member accesses

mansellan

Sorry I'm probably not explaining very well...

IEnumerable is just something you can progress through, from start to finish, in sequence.

and object is basically "something"

so, if you have "something1", "something2", "something3" - how do you know that the first 2 are on the first row, and the thied is on the next row?

IvenBach

You don't and can't know. You need some inkling of a structure. How it's formatted to know that. Similar to encoding.

mansellan

I think you need to pass something other than IEnumerable<object>to your function, because by that point you've lost the information you need to make a 2d array.

IvenBach

11:44 PM

You are right.

I think I'm too close to the code right now and need to step away to think about it for a while.

mansellan

If you had IEnumerable<IEnumerable<object>>, a list of rows, each of which was a list of cells in the row, you'd be in a better place. But I suspect there may be a more specific structure possible

(Just from looking at that 1 line, haven't looked at the PR in the round)

Mathieu Guindon

rule of thumb, using object in .net code is a smell

mansellan

^

IEnumerable<T> on the other hand, is often correct, per Liskov.

IvenBach

I tried T but I don't know how to indicate what it is. I don't use generics often enough.

5 mins ago, by IvenBach

I think I'm too close to the code right now and need to step away to think about it for a while.

Duga

[rubberduck-vba/Rubberduck] build for commit 46271afa on unknown branch: AppVeyor build succeeded

IvenBach

11:51 PM

I need to mull it over in my brain and come back to it with fresh eyes. Reviewing each result that's being supplied to refactor it to a more appropriate type.

mansellan

@IvenBach So in IEnumerable<object>, T is object. In IEnumerable<string>, T is string.

IEnumerable<T> just means "An IEnumerable of something, which will be decided when I declare it. T could be string, object, Foo...

this

@IvenBach have you inspected the contents using debugger?

it'll tell you and you can then be more specific

mansellan

Put another way, before generics, we just had IEnumerable. Each element was an object, so each element could be anything. A string, and integer, a Foo... there was no guarantee that any element would be anything like the one before.

Now that we have generics, we can say IEnumerable<string>, and the compiler will guarantee that every element has to be a string.

So, IEnumerable<T> just means "An IEnumerable where you can decide what type the elements will be"

Mathieu Guindon

...without incurring boxing when T is a value type

hence ArrayList being deprecated ever since

mansellan

Also, see Java generics, where it can't make such guarantees, so....

;-)

this

11:59 PM

@MathieuGuindon I wonder if deep underneath, ArrayList is the root of it all.

Transcript for