I said something along the lines of "C# allows you to do a lot more than VBA. After learning a .NET language VBA feels restrictive." And that's where the implied non-VBA comes from. Honest to a fault I guess.
I'll still bring it up with my current employer that I've had a couple interviews. I'm worth a lot more than I'm paid and worst that can happen is I get told "No pay increase".
Thanks for the support nonetheless. I appreciate it.
next time try "after learning a .NET language VBA feels restrictive I feel like my understanding of VBA and my overall programming abilities have tremendously improved; my code is clearer, cleaner and faster than ever. Plus there's Rubberduck. You know about Rubberduck?" ;-)
Me too. I'd rather me getting a .NET related job sooner rather than later. more time to learn from others. A pay increase is part of it but not the driving force in considering the position.
My boss may panic a bit with me bringing it up though. 2 people already left this year for more pay. I'm the only coder though. That's the biggest issue if I leave. #NobodyElseKnowsTheCode
To be strictly honest, I knew that would happen when you came back without a scheduled interview tomorrow.
In my experience, when they are pressing forward that aggressively and they already told you the tentative schedule, they schedule them at the end of the last one.
> There are a number of InspectionResult resource types for the UnreachableCaseInspection (UCI) that probably require modification if the 'unreachable' result-type does. Based on the above input, I've enumerated them below with some suggestions. I'm thinking it is probably better to hash out the wording here, rather than on the PR.
A couple comments: 1. It seems to me that 'algorithmically' would be a more precise descriptor than 'heuristically'. A heuristic (full disclosure - I had to l
> There are a number of InspectionResult resource types for the UnreachableCaseInspection (UCI) that probably require modification if the 'unreachable' result-type does. Based on the above input, I've enumerated them below with some suggestions. I'm thinking it is probably better to hash out the wording here, rather than on the PR.
A couple comments: 1. It seems to me that 'algorithmically' would be a more precise descriptor than 'heuristically'. A heuristic (full disclosure - I had to l
> I see. The thing is that I wouldn’t call it “malformed”... I would refer to it as logically impossible or self contradictory... the problem here isn’t the syntax or grammar (e.g. it is well formed) but rather the logic. The messsage should pount to that.
Ivens-Duckling: Daddy it's so cold outside.
Iven: mumble mumble Mug mumble ---Canadian--- Russian winters mumble.
Ivens-Duckling: What's that mean?
Iven: You've no idea what cold is. Neither does Daddy.
@Hosch250 I'm not that let down. Reading the description I already felt a bit out of my league with all the DB it would have entailed.
Would have been a 50% pay raise though. That will be missed.
i want to increase the performance of this code:
Dim...
...
...
...
...
Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True
Set wb = objExcel.Workbooks.Open("C:\Dateipfad\Dateiname.xlsx", True)
Set rs = db.OpenRecordset("Select DataPointVID from My_ValidReport", dbOpenSna...
Note that the Connection changed from keep-alive to close.
@Hosch250 I was just re-reading and saw that. Is there possibly something to that? is there something I can set in my WinHttpRequest to force the change from my end?
I don't believe I've intentionally made any changes to that effect in Postman, but I'm bumbling my way through and may have flipped a setting somewhere...
Given a `System.Type` of an ANTLR-generated parser class, how can I get all the generated parser rule context types? My first thought is to return all the types returned by any of the methods of the parser class, as long as they inherit from `Antlr.Runtime.ParseRuleContext`. Will this be accurate, or are there some rule context types which don't have a corresponding method on the parser class? Is there another way to go about this? (I need it for https://github.com/zspitz/ANTLR4ParseTreeVisualizer/issues/8.)
@Hosch250 I think I ended up showing Postman pics of both the request and the response, but I think your comment was directed at the response header pic. (I think...)
Can I actively enable Keep-alive when I make the request? Would that (possibly) have any notable impact?
In the meantime, I've sent in a support ticket to the vendor. We'll see if I get a response to this one. They're on Iven time (PDT) so it'll be a while before they even see it. :/
Looking now, I see that in Rubberduck, for example, StartRuleContext doesn't inherit directly from Antlr4.Runtime.ParserRuleContext, but from Rubberduck.Parsing.Grammar.VBABaseParserRuleContext. Is this always the case? Or do the context classes sometimes inherit directly from ParserRuleContext?
@Hosch250 I don't really have access to the grammar at runtime, only Type instances corresponding to the auto-generated classes. So I can't rely on the preamble in any case.
(NB. There's a little voice in my head saying, "the ANTLR4 API was written in Java -- extracting out any bit of information feels like pulling teeth.")
> How about a more direct message rather than general descriptors...
_UnreachableCaseInspection_InherentlyUnreachable_ **Existing:** Unreachable: Case Statement contains invalid range clause(s). **New:** 'Case' statement Range Clauses must be expressed '[x] To [y]' where [x] is less than or equal to [y]'
> **Justification** In large projects, the amount of code in each class can get unwieldy. For example, in one class I have a large number of defined properties which overwhelm the subs/functions in the class. Visual Studio/C# allows the user to mark certain areas of code as a named region which they can then collapse in the editor window to hide from view when working on other areas.
Right now I'm marking the areas using the following syntax: `'#Region Properties` and `'#EndRegion`
> As it stands, we can't add collapsing to the VBE just yet, because we didn't find a reliable way to control the codepane of the VBE. When we get to hijacking the editing process with our own avalon pane, scopes will become collapsible.
That being said, even if we have codepanes under our control, I personally very much dislike regions as a tool. As such I'd argue against implementing regions for Rubberduck, if only because I consider them an anti-pattern.
Are we sure we want to decline this, though? The argument that #region is an anti-pattern is because we should be refactoring code into smaller units or whatever. But does it hold up in VBA? Take factory method for example. That can generate a substantial boilerplate code that would be otherwise distracted and cannot be moved without breaking abstraction/encapsulation?
I finally finished my first code which is supposed to extract information from a selected document into a template. its a really large template and therefore I have massive amount of lines. I really hoped you could help me!
Sub Test2()
' Test2 Macro
Dim FileName As String
FileName...
Hmm, I think the region-hatred is a little OTT. Yes, they're easily abused, but used sparingly they can be useful sometimes.
I used to be in the "OMGZ regionise all the things" camp, got ripped into it at work, then looked into it and realised it was cargo-cult. So now I rarely use them, but occasionally they help.
@MathieuGuindon Re: Lingering Excel process. Over the past 3 hours I've not had any issue. I'm certain it's not RD and fault lies with the other program.
in other news, I think I have something like the beginning of a CPA engine that can handle GoTo and GoSub/Return jumps. I'm hoping to be able to write a first test tonight - if all goes as planned, I'll have an ExecutionContext for each code path, and the next problem to solve will be to "merge" paths (e.g. code after End If should be part of the conditional path)
@IvenBach :+1:
@mansellan meh.. if it's just @Vogel612 and me vs. everyone, custom folding might just happen over-my-not-so-dead-body anyway
> So I'd like to make some counter-arguments here. First, some context. I used to use regions almost exactly as illustrated in @samcan 's post. Code felt cold and foreign without it. When I joined my current employer, I was challenged on it after my first commit, as no-one else did it, and they universally hated that I did it. It took a while, and some reading of posts like the one above, for me to let go of the habit, and to be honest, I haven't missed it one bit. Especially after I found Ctr
@MathieuGuindon what's stopping us from doing '@Todo blah blah with @End Todo? That would end up enhancing the todo explorer in giving us a section for where the todo applies?
> Just to toss out a different take.... because we do want to encourage people to refactor their code rather than hiding the complexity, it might be more desirable to enable code folding over TODO markers (which implies creating a end marker for the same TODO). That would in turn encourage people to always label the section as something needing to do and hopefully encourage them to compose their code some more so that it's no longer necessary to fold code.
I looked at the StackOverflow answer regarding regions, and while I get what it's trying to say about splitting a class into smaller classes as a class is doing too much, I don't feel like that's always applicable. In the project I'm working on right now, I've got about 15 properties for a class, which, because VBA has a very verbose implementation of properties, is overwhelming the number of subs/functions I have in my class, and the pieces are all directly related to the class they're
@Duga I think to go further, we need examples to show whether we can actually compose a class or not. Talking in abstract is easy but to actually apply with VBA's limitations is another thing.
> @samcan keep in mind that while the vast majority of the literature on OOP/SOLID is perfectly applicable to VBA, some of it remains impossible to do - e.g. in C# you could make a class `partial` and split it across different files; in many languages you can abuse inheritance and move members to a base class. I'm not sure there are many downsides to moving a class' *default interface* properties into a tightly-coupled DTO (that DTO class could even be reused as a factory method parameter), eff
> My only concern is that these changes could be easily missed during translation of the resources - could the corresponding keys be removed from the other .resx files? Also does the [xmldoc examples](http://rubberduckvba.com/Inspections/Details/UnreachableCase) could probably use a refresher; the website theoretically supports multiple examples (each example needs to have a `hasResult="true"` or `hasResult="false"` attribute). Would that be in-scope for this PR?
> My only concern is that these changes could be easily missed during translation of the resources - could the corresponding keys be removed from the other .resx files? Also the [xmldoc examples](http://rubberduckvba.com/Inspections/Details/UnreachableCase) could probably use a refresher; the website theoretically supports multiple examples (each example needs to have a `hasResult="true"` or `hasResult="false"` attribute). Would that be in-scope for this PR?
Going to a symposium tomorrow to suffer death by Powerpoint. Each speaker has been allocated 30 minutes including questions/discussion. There is not one speaker who has less than 20 slides. One has 68 slides!!!!
@Freeflow the best powerpoint slides have pretty much nothing on them. hopefully you're not going to get bombarded with overcrowded slides... kinda hate it when presenters end up just reading their slides.
Welcome to CR! You're about to be told why using namespace std; shouldn't be used, and how a monolithic sequence of executable instructions can be turned into small, specialized procedures that do nothing more than what their name says - I hope you learn as much on this site as I did! In the meantime feel free to browse other rock-paper-scissors posts for more ideas and tips, as each post contains a working implementation and very valuable inputs from reviewers. — Mathieu Guindon22 hours ago
@MathieuGuindon > "Should be an answer not a comment."
i cant seem to get my loops to work right in VBA hoping im missing something simple. Im trying to index thru a specific folder and has tons of files in it and for each file that ends with ".dwg" i want to do create a script (one script for all dwgs files thats why i need to index thru them to get...
Public Function ColumnsTwo(ByVal sourceRange As Range, Optional ByVal DELIMITER As String = ",", Optional ByVal canRemoveFromFront As Boolean, Optional ByVal canRemoveFromCenter As Boolean, Optional ByVal canRemoveFromTail As Boolean) As String is the signature.
When trying to run it in the immediate window I get Sub or Function not defined
Grrrr why did I even get anywhere near that post....
@together note that I can't do telepathy, and can't see your screen - going to need a lot more meat than "doesn't work" to help. — Mathieu Guindon1 min ago
i want to increase the performance of this code:
Dim...
...
...
...
...
Set objExcel = CreateObject("Excel.Application")
objExcel.Visible = True
Set wb = objExcel.Workbooks.Open("C:\Dateipfad\Dateiname.xlsx", True)
Set rs = db.OpenRecordset("Select DataPointVID from My_ValidReport", dbOpenSna...
VBA Rubberducking
VBA Rubberducking