Version 2.4.1.4940 OS: Microsoft Windows NT 10.0.18362.0, x64 Host Product: Microsoft Office x64 Host Version: 16.0.12026.20108 Host Executable: WINWORD.EXE
**Description**
I'm getting the following inspection result, but the variable highlighted when I double click the inpsection report is not that referred to by the inspection report
Error: In a context that requires a value type, the expression 'Split(p.Value, mySeparator)' of object type
> No problem. I've attached the source code file. Please be aware that I am not a professional programmer have only previously coded in VBA (apart from some 6502 assembly and a small amount of ANSI C back in the 1980's doing image processing stuff for my PhD). This was my first foray into c# and it did take a few months googling and trial and error to get to the current state. I'm currently working up courage to put it up on code review for comment.
Why does Excel (in both 2016 and 365) refuse to show me the DATEDIF() function when I type =DAT in a cell? It shows me DATE and DATEVALUE, and that's it.
#BecauseMicrosoft <-- self-answer, upvote, accept
according to their documentation, it's been around a while (like since 2010)
It's almost like they want you to do (StartDate - EndDate) / 365 to get the elapsed years...
Context
I'm trying to create a multi-series chart/infograph to display total number of sales for the day as compared to the average. The chart consists of three series:
Series 1: The base bar graph showing the number of each item sold
Series 2: A scatterplot to overlay the icons for each item ...
Maybe that'll clarify- before I asked for the interface definition - I had wondered that if there was a recursive default member that might cause it to be implicit (e.g. p.Value.Value) or something like that. But now we can see that this can't be the case since there should be no default member access for this particular class.
@MathieuGuindon last year rather but yeah, resolver was before that time
so that's a good reason. I guess the question ought to be -- ought we be using it now that we have type info for everything?
one sucky aspect, though, is that for user code type infos, it's one threaded and on UI thread, too
so no parallelizing nor background threading
but that shouldn't be a restriction for the non-user-code type infos, though.
However, it says the ITypeComp exists to provide a fast access for that data. If it is in fact fast, it might help cut down on the resolution time, and could be at least batched
Totally random question. Why do we have usings outside the namespace? I've always seen it outside but I noticed that there are times where they put it inside the namespace.
yeah, I figured that much. Still, it makes me wonder - I always presumed the using directives were file-scoped. I don't know for sure but also presume that that is still true even inside a namespace --- unless the file had more than one namespace (in which the file is FUBAR)
There is actually a (subtle) difference between the two. Imagine you have the following code in File1.cs:
// File1.cs
using System;
namespace Outer.Inner
{
class Foo
{
static void Bar()
{
double d = Math.PI;
}
}
}
Now imagine that someone adds an...
@FreeMan well, sorta... If it's a big wall, it's probably telling you you have too many namespaces. I tend to prefer having folders go "deeper" than namespaces...
@M.Doerner well, the binding would point to another ITypeInfo representing that thing being bound. Therefore, if a declaration was mapped to a given ITypeInfo, then we would be able to bind a name expression to one such declaration.
Right now, resolver has lot of binding logic. If ITypeComp::Bind did the same work for much less, then it's easier for us to convert a ITypeInfo reference into a declaration reference.
Currently, we try in a sensible order based on the expression classification of the binding of the lExpression.
We might be able to use it for the member access bindings and simple nema bindings, but we need those as intermediate steps in the remaining resolution.
1. You wrote that when double-clicking something else than the reported expression is highlighted. Could you please tell us what is selected when you double-click. That might help us find the issue. 2. Could you also tell us how exactly `p` is declared. That might also help.
So far, I have not been able to reproduce this issue ar any discrepancy between the selection and expression.
Final stupid question, just in case: you have not defined a public funct
Summary: Open Source Stack Exchange will begin the nomination stage for a special election on September 16 to bring in one more moderator.
For full details of the process, see the announcement on Meta Stack Exchange. The timeline:
Starting on September 16, users can nominate themselves. Users ...
> A program is free software if it gives users adequately all of these freedoms. Otherwise, it is nonfree. While we can distinguish various nonfree distribution schemes in terms of how far they fall short of being free, we consider them all equally unethical.
Does that mean it's unethical for a high-rise builder to charge their clients for building buildings?
I'm just a bit curious as to where the line falls. I know it's different for everyone, but if all software was free, and businesses only made money off support, I'm not sure that's sustainable.
The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
I understand GPL--especially for projects like RD where people could easily make a living off it.
But again, I understand view-only ones, where people share it mostly for security purposes, but want to keep a monopoly on the sale of it.
Or whatever people share it for.
Personally, I like Apache 2.0 for side projects, and if I ever decided to make the effort to sell it, I'd just take the project off GitHub and add the killer features before I tried.
something feels off with this. anyone here sees a way to rephrase it better?
var response = _request.RequestItems(args);
var content = response.GetContent();
var items = content.Items;
var cursor = response.GetNextPageCursor();
do
{
if (!string.IsNullOrEmpty(cursor))
{
_logger.Trace($"Response header yielded a page cursor. Requesting next page.");
response = _request.RequestItems(cursor, args);
content = response.GetContent();
I had a nicely working paginated requests setup, and now Shopify is pulling the rug from under my feet by removing the "page" argument from the GET url, and adding "next" and "previous" page "cursors" in the response headers... and gosh, what a mess.
hmm and how do they know that the model is correct? That's the hardest thing about the math - you can make proof of anything in abstract but it doesn't mean it correspond to the physical reality?
It's basically a "proof" language built in F# and another language.
You write the proof, and it generates the output.
I learned about it from the Roslyn team, and they use it some for language implementation.
> After verification, F* programs can be extracted to efficient OCaml, F#, C, WASM, or ASM code. This enables verifying the functional correctness and security of realistic applications. The main ongoing use case of F* is building a verified, drop-in replacement for the whole HTTPS stack in Project Everest. This includes verified implementations of TLS 1.2 and 1.3 and of the underlying cryptographic primitives.
> F* is written entirely in F*, and bootstraps in OCaml and F#.
@MathieuGuindon also, in that case, that implies you need to orchestrate the read and the update, so possibly a 3rd entity, so that the reader can hide the silly pagniation while providing a faithful representation of the records accessed in same order, simplifying hte update.... hopefully.
@this yeah... I'm hitting essentially every endpoint there. I'm not worried about that part for now - but something itches about the duplication of string.IsNullOrEmpty checks... eh, I'll just ...let it be and move on... tomorrow.
> Your stupid question is entirely correct in its surmise. I am stupid, I will go and stand in the corner with my pointy hat on for the rest of the evening. The code in question should of course read VBA.Split... Which of course raises the follow on inspection thought that VBA has missed this duplication of names so maybe its a job for rubberduck?
BUT what would be causing a similar error in the following case
``` '@TestMethod("HelperForStrings") Private Sub T2A_Stringify_object()
> I have to correct myself, the problem is not strictly with param arrays but with the type names provided for arrays by the part of RD that loads libraries. It adds parentheses to the type name ,if the type is an array. This interferes with the check for the parameter type Variant for param arrays.
Context
I'm trying to create a multi-series chart/infograph to display total number of sales for the day as compared to the average. The chart consists of three series:
Series 1: The base bar graph showing the number of each item sold
Series 2: A scatterplot to overlay the icons for each item ...
There is actually a (subtle) difference between the two. Imagine you have the following code in File1.cs:
// File1.cs
using System;
namespace Outer.Inner
{
class Foo
{
static void Bar()
{
double d = Math.PI;
}
}
}
Now imagine that someone adds an...
Summary: Open Source Stack Exchange will begin the nomination stage for a special election on September 16 to bring in one more moderator.
For full details of the process, see the announcement on Meta Stack Exchange. The timeline:
Starting on September 16, users can nominate themselves. Users ...#/media/File:AjaxBicloro.jpg){kind=link}
VBA Rubberducking
VBA Rubberducking