Printable View
For example, I ask. What does Claude Pro do (better or?) other than Claude Free does not do in regard to VB6 programming assistance? I have found the Claude Free and CoPilot make newbie mistakes like using inappropriate variables in a For Each loop and then at my pointing out the error uses a For Next rather than changing the variable type. Then a week or so later, they make the same mistake.
We are less ignorant than AI it seems.
Yes, it has a couple of issues. It uses sometimes forbidden keywords as variable names.
It declares API between procedures.
And it declares variables in any place. That's not a mistake because VB6 allows that, but not everybody would like that.
But there is a solution. Claude has "Memory". It is a place for things that you want to tell it once and remember for every chat.
So, you can tell it the things that you want it to remember, so you can ask it to save those in its memory.
These are the rules it has for Memory in my account configuration:
You can ask it to add these rules and save them to the memory of you can do it yourself: go to your account icon at the bottom left, Settings, Capabilities, ensure that you have "Generate memory from chat history" set, then click "View and manage memory" and you can read or edit the memory there.Code:VB6 Programming Rules — apply strictly to all VB6 work:
Environment: VB6 classic.
Unicode APIs: Always use W-suffix Win32 functions (SendMessageW, GetWindowTextW, CreateFileW, etc.).
API Declarations: All Declare statements go strictly in the General Declarations section at the top of the module — never between procedures.
Variable Declarations: All Dim statements grouped at the very top of each function/sub.
Syntax restrictions: Never use reserved keywords as variable names. Minimize line continuation underscores (_); never place a comment after _ (compile error).
Naming: Never use single-letter type-suffixed names (iF, iS, iI, etc.) — invalid in VB6. Use full descriptive prefixed names (lFileNum, sLine, lIdx, lLoop, etc.).
Reserved words to never use as identifiers (compile error or silent misbehavior): Abs, AddressOf, And, Any, Array, As, Attribute, Boolean, ByRef, Byte, ByVal, Call, Case, CBool, CByte, CCur, CDate, CDbl, CDec, CDecl, CInt, CLng, Close, Const, CSng, CStr, Currency, CVar, CVErr, Date, Debug, Decimal, Declare, DefBool–DefVar, Dim, Do, DoEvents, Double, Each, Else, Empty, End, Enum, Eqv, Erase, Event, Exit, False, Fix, For, Friend, Function, Get, Global, GoSub, GoTo, If, Imp, Implements, Input, Int, Integer, Is, LBound, Len, LenB, Let, Like, Local, Lock, Long, Loop, LSet, Me, Mod, New, Next, Not, Nothing, Null, On, Open, Option, Optional, Or, ParamArray, Print, Private, PSet, Public, Put, RaiseEvent, ReDim, Preserve, Rem, Resume, Return, RSet, Scale, Seek, Select, Set, Sgn, Shared, Single, Spc, Static, Stop, String, Sub, Tab, Then, To, True, Type, TypeOf, UBound, Unlock, Until, Variant, Wend, While, With, WithEvents, Write, Xor. Also avoid common shadowing names: text, index, key, item, count, left, right, top, width, height, font, color, enabled, visible, caption, value, tag.
DPI rule (strict): Never assume fixed 96 DPI. Always calculate dynamically using Screen.TwipsPerPixelX / Screen.TwipsPerPixelY, or ScaleX / ScaleY as appropriate. All projects must work correctly at any DPI setting.