This isn't the expected format of a message in this topic.
Please do not comment on what your
Eclecta says about formatting. It does its job perfectly, but it can't yet sense multiline comments in between /* and */
and multiline string literals in between " and "
if they span across several lines
in your code editor. FBSL supports both of them but your Eclecta's formatter can't yet track them property and still tries to format what's there in the lines that fall in between the opening /*
and a matching closing */
a few lines below. That's a known false-positive issue that's described in your Eclecta help file.
Further, you aren't supposed to mechanically delete all #DllDeclare's you're seeing, but only those of them that would read #DllDeclare Kernel32(bla, bla, bla, ...)
, or #DllDeclare User32(bla, bla, bla, ...)
, or #DllDeclare Gdi32(bla, bla, bla, ...)
. Instead, you've attempted to delete a valid directive that refers to a library which isn't among the three ones I pointed out: #DllDeclare Zlib(bla, bla, bla, ...)
. That's not a proper thing to do; zlib.dll is a 3rd party compression library whose APIs must
be declared explicitly.
Finally, when you are answering a message, do not use the Quick Reply button. Prefer to use the POSTREPLY
button that would open up a full featured editor with a range of text formatting options. At the top of your editor, you will see the topic title Re: Examples broken in v3.5
. Modify it e.g. as follows Re: Examples broken in v3.5: DllDeclare
. Then we'll know what's in your message when we're looking through the list of topics' contents. When in the editor, among the text formatting buttons right above your message text you will see a button called Code
. Click it and it will add a couple of code tags. You are supposed to copy to the clipboard the entire example preformatted in your Eclecta and paste it in between
the opening [ code ]
tag and the closing [ / code ]
tag (without spaces which I added here to be able to let the tags be shown at all, otherwise my editor would interpret them literally and add code quotation as follows: )
- Code: Select all
bla bla bla
I do not want to lose my time paging through the help file myself searching for the code you are referring to. I'd like to see it here in its entirety, preformatted for me to copy-paste it to my Eclecta, add a quick fix, and copy-paste it back to the Examples runnable in v3.5
P.S. Object 'MB_YESNO' isn't found
is an indication that you have to add a #Include <Include\Windows.inc>
directive. FBSL v3.5 has all
of Windows constants collected in the Windows.inc include file and adds them selectively to your code when needed. v3.4 used its built-in library "@|Win32" for that purpose, but the library contained only a few of such constants but itself made the Fbsl.exe and Fbsl.dll binaries much fatter than they should've been. This is an "error" you're going to see very often when trying to run v3.4 examples in v3.5. At the same time, do not add this directive mechanically to all the examples you check. It is a bad programming style
to include files that aren't exactly necessary for your code. I wouldn't like to see any more of such ill-mannered bloat as #Uses "@|Win32"
in every example throughout the FBSL BASIC documentation.