Issue #19 resolved

Generation fails

Anonymous created an issue

The following call of LoadGen produces an error:

C:\Libs\glLoadGen_0_3_1>lua LoadGen.lua exp/3.3 -version=3.3 -profile=compatibility -style=pointer_cpp

lua: ./modules/TabbedFile.lua:44: bad argument #2 to 'format' (string expected, got nil)
stack traceback:
        [C]: in function 'format'
        ./modules/TabbedFile.lua:44: in function 'fmt'
        ./modules/StylePointerCPP.lua:178: in function <./modules/StylePointerCP
P.lua:175>
        (tail call): ?
        ./modules/Structure.lua:322: in function 'PreProcess'
        ./modules/Structure.lua:123: in function 'Process'
        ./modules/Structure.lua:144: in function 'ProcessChildren'
        ./modules/Structure.lua:195: in function 'IterateChildren'
        ./modules/Structure.lua:563: in function 'PreProcess'
        ./modules/Structure.lua:123: in function 'Process'
        ...
        ./modules/Structure.lua:127: in function 'Process'
        ./modules/Structure.lua:144: in function 'ProcessChildren'
        ./modules/Structure.lua:127: in function 'Process'
        ./modules/Structure.lua:144: in function 'ProcessChildren'
        ./modules/Structure.lua:127: in function 'Process'
        ./modules/Structure.lua:144: in function 'ProcessChildren'
        ./modules/Structure.lua:127: in function 'Process'
        ./modules/Structure.lua:734: in function 'Proc'
        LoadGen.lua:63: in main chunk
        [C]: ?

However, the command line call ">lua LoadGen.lua exp/3.3 -version=3.3 -profile=compatibility -style=pointer_c" (notice the different style parameter) works (but the files fail to compile, see my other bug report).

Comments (3)

  1. Jason McKesson repo owner

    Fixed in e9576bf .

    I'm going to make a 1.0 release either tonight or tomorrow, and these fixes will be in that. However, if you want to download them beforehand, just go to the downloads page, click on "Branches" and download the 0.3 branch. That should tide you over.

    Also, thank you for providing a complete bug report, with command-line and full output. It was of great help in tracking down the problem.

  2. Log in to comment