I think things have a chance of starting of get easier to implement from there.
I'll write a couple of other tests, and then I'll put up the Parser class on CR, commit / push my changes, and then create a new issue for each language construct that needs an ISyntax implementation.. and the parser should just automagically "understand" them as they get added.
I usually put a breakpoint on the return result; line in the Parse method, and then launch the debugger and find a module I want to parse, and click "Parse module" from the Rubberduck/Refactor menu.
ah, works now.. except it's parsed as a CodeBlockNode
@RubberDuck everything that has child nodes will be treated as a CodeBlockNode... think Enum, Type, For...Next, If...Then...Else, etc. - should we have EnumNode, TypeNode, ForNode, etc., or we can walk away happy with CodeBlockNodes?
but CodeBlockNode isn't abstract, so I'm newing it up as a CodeBlockNode, which causes everything to be a "code block" with impossible upcast to EnumNode
The story...
A bit of background info and how is the database designed...
Please notice you don't really have to rebuild the tables in SQL but I shared an SQL Fiddle just in case and screenshots1 of what the database looks like. I thought it was going to be easier to explain the story of what I...
I hear that Nullable<T> is a C# generic class and it does not work with COM - like any other generic class.
Well, in my C# class library I have:
[InterfaceType(ComInterfaceType.InterfaceIsDual),
Guid("2FCEF713-CD2E-4ACB-A9CE-E57E7F51E72E")]
public interface ICOMClass
{
int? GetNullable();
}...
Each SyntaxTreeNode has an Instruction, and each Instruction knows its StartColumn, EndColumn and LogicalCodeLine - and there's a module line number for each LogicalCodeLine. So we can make a Selection out of any SyntaxTreeNode pretty easily.
at the end of the day, it's what we decide to make it ;)
but so far I've used it for when the parser needs to "enter a code block" and "scan" an unknown number of logical code lines to complete the code block node.
like, an EnumNode is one, TypeNode is another; ProcedureNode is obviously one, IfBlockNode also, and then everything else I can think of just works that way too... I guess it's right.
Development. Basically I want a faster ability to "hit button and start debugging" route than having a stop/debug.assert statement or manually going into the form VBA (either through design mode --> "on action" or find/etc)
When I submit the requests, I take the new rows from each and put them into individual workbooks by themselves, which has additional information including the above tab.
@cheezsteak the best answer to "why" right now is: "because"
(that's partly why I'm here, trying to improve all this mess)
Upon saving each individual file (usually 4-6 Excel files) I have to create a Jira ticket for each, and attach them, and await approval and processing, upon which I go back to the workbook with all the tabs and update the rows
Not to a great extent. I'm limited to restructure how the requests are added (the first workbook) and how they are saved (the 2nd screenshot)
Anything after that (the Jira tickets, approval, processing) I have no say into. I have authority on how the workbook is updated as requests are submitted and processed.
If there was something that could fetch the records from each table where the ticket number/date submitted are null, save an Excel file with today's date into a folder, that would start saving me a lot of time...
I then have to take the contract numbers and feed them into an old VB application using a separate Excel file, so that the Jira ticket information is documented in each record in our actual business DB.
And then the information will become documented in SNAP for anyone in the business to access.
Sub LeadingZeros(ByRef rng As Range, ByVal zeroes_count As Integer, _
Optional ByVal other_char As String = "0")
Dim zeros As String
zeros = ""
Dim iz As Integer
For iz = 1 To zeroes_count
zeros = zeros & other_char
Next iz
rng.Cells.NumberFormat = zeros
ReloadValue rng
rng.EntireColumn.AutoFit
On Error Resume Next
Dim txt As Variant
Dim area As Range
For Each area In rng.Areas
Dim c As Range
For Each c In area.Cells
Dumb people who set up the database years and years ago decided that SQL-native IDs generated when records are inserted were too simple. So they made seeding tables instead to get IDs from. So they have to go back every couple months and make more IDs.
The story...
A bit of background info and how is the database designed...
Please notice you don't really have to rebuild the tables in SQL but I shared an SQL Fiddle just in case and screenshots1 of what the database looks like. I thought it was going to be easier to explain the story of what I...
The story...
A bit of background info and how is the database designed...
Please notice you don't really have to rebuild the tables in SQL but I shared an SQL Fiddle just in case and screenshots1 of what the database looks like. I thought it was going to be easier to explain the story of what I...
VBA Rubberducking
VBA Rubberducking