Announcement

Collapse
No announcement yet.

Look what I found...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Look what I found...

    Hey Guys!


    try this...

    Code:
    #compile exe
    
    function FormFeed as long
    end function
    
    function pbmain as long
    end function

    why on earth does this not compile when "FormFeed" doesn't seem to be a "reserved word". If it is then the documentation failed to say it. I wanna know Lance, what does this function/statement do???

    Also, is there any way to get a COMPLETE list of reserved words for PBDLL



    ------------------
    Cheers

  • #2
    Strange thing, Mark!

    Typing it in the PB-editor, it becomes highlighted, which should mean it IS a keyword.
    The only place where I can find it in the helpfile is in connection with MOD (an operator). It shows a strange example, however, about printing lines. AS a PBDLL user, this does not make sense to me.
    My conclusion is that its keyword status is a 'bug', perhaps.

    ------------------
    mailto:[email protected][email protected]</A>
    www.basicguru.com/zijlema/

    Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
    http://zijlema.basicguru.eu
    *** Opinions expressed here are not necessarily untrue ***

    Comment


    • #3
      There's no mystery, and no bug... FORMFEED is a PB/CC keyword. PowerBASIC often reserves keywords from its other languages 1) in case that keyword in needed in more than one language, 2) so that a single keyword list can be maintained for use by various editors, 3) etc.

      -- Eric


      ------------------
      Perfect Sync: Perfect Sync Development Tools
      Email: mailto:[email protected][email protected]</A>

      [This message has been edited by Eric Pearson (edited February 02, 2001).]
      "Not my circus, not my monkeys."

      Comment


      • #4
        That's interesting.
        I write a lot of stuff for Postscript printers and the other day
        I got a PS data file into memory and, after changing and saving
        it, I found it kept producing a PS error when sent to the printer.
        Investigation shows that the word "show" which must be in lower
        case in a PS file, was converted to "SHOW".
        I recalled another PS file into PBDLL6 and every "show" was
        converted into blue caps as a PBDLL keyword.
        I couldn't find it in the PBDLL manual.
        Regards,
        Brian


        ------------------
        Brian.

        Comment


        • #5
          Eric, Lance, anyone.

          Eric is correct, my PBDLL60 still complies most of my legacy applications all the way back to TurboBasic, I'm so confused that I need to put a comment at the top of every Source file as to which compiler I was using at the time.

          See the PB3.5 keyword list and NEVER use any keywords as variables, PB has retained more backward compatibility than any compiler I know.
          To doccument ALL KEYWORDS in new releases, would confuse new users.

          In the PBEditor, certian words (I think it is DIALOG) don't link to the proper topic when I place the cursor on the word and hit F1.
          I get the main help tree.

          Can I recompile the word list, do I have an old version of help, and/or can I edit the help file.


          Mike...


          ------------------

          Comment


          • #6
            Brian --

            DIALOG SHOW MODAL
            DIALOG SHOW MODELESS
            DIALOG SHOW STATE

            ...are all PB/DLL DDT functions.

            -- Eric


            ------------------
            Perfect Sync: Perfect Sync Development Tools
            Email: mailto:[email protected][email protected]</A>
            "Not my circus, not my monkeys."

            Comment


            • #7
              Eric,

              More or less I'm willing to accept that FormFeed is a PB/CC keyword and therefore 'acts' in the same way in PBDLL.
              What I don't understand, however, is how it is possible that the strange MOD example got lost in the PBDLL helpfile.

              Lance?

              ------------------
              mailto:[email protected][email protected]</A>
              www.basicguru.com/zijlema/

              Egbert Zijlema, journalist and programmer (zijlema at basicguru dot eu)
              http://zijlema.basicguru.eu
              *** Opinions expressed here are not necessarily untrue ***

              Comment


              • #8
                Bugs happen. Let us know when you find them, and you'll find that we fix them.

                ------------------
                Tom Hanlin
                PowerBASIC Staff

                Comment


                • #9
                  IMO the MOD example is not a "leak" of a PB/CC keyword over to the PB/DLL Help File, because the PB/CC syntax is LPRINT FORMFEED, not just FormFeed. I think it's intended to be a plain-English, self-exaplanatory example of how MOD might be used in a real-world program. Perhaps the fact that PB/DLL doesn't support printer output makes it less than apt, but it serves the purpose.

                  -- Eric

                  ------------------
                  Perfect Sync: Perfect Sync Development Tools
                  Email: mailto:[email protected]com[email protected]</A>
                  "Not my circus, not my monkeys."

                  Comment


                  • #10
                    IMO the MOD example is not a "leak" of a PB/CC keyword over to the PB/DLL Help File, because the PB/CC syntax is LPRINT FORMFEED, not just FormFeed....
                    Same "leak" as "HANDLE", which of course is only a reserved word in the context of an OPEN HANDLE statement.


                    My real "wish list" for PB.next is to clean up all this stuff, like not allowing "Formfeed" in PB/DLL or PB/CC even when not misused as a keyword.

                    Here, try this one:
                    Code:
                    FUNCTION X (Seg as LONG) AS LONG
                     FUNCTION = 1
                    END FUNCTION
                    Cute, how the parser still uses the MS-DOS compiler logic.

                    MCM

                    Michael Mattias
                    Tal Systems Inc. (retired)
                    Racine WI USA
                    [email protected]
                    http://www.talsystems.com

                    Comment

                    Working...
                    X