Lua Mock Api docs from engine source

[PicassoCT]

Hi,
im trying to convert the documentation for the LuaApi int a loadable Mockup.
Not much to look at at the moment, due to Regex Fail.
Where did i go wrong?

ConverterRegex:

Code: Select all

(?P<Spring>Spring\.)(?P<FunctionName>[a-zA-Z0-9]+)([^\(]+\()(?<ArgPair>(?<ArgType>[a-zA-Z0-9]+)\W+(?<ArgName>[a-zA-Z0-9]+)([^a-zA-Z]+))+([^>]+>)([^\S]+)(?P<ReturnType>[a-zA-Z]+)

OutPutPattern:

Code: Select all

$Spring$FunctionName = function $FunctionName($Arguments)assert("$ArgumentType" == type($ArgName); return Mock$ReturnType end

https://github.com/PicassoCT/SpringLuaApi

[abma]

sorry, can't directly help with your problem but i moved the topic to engine development as only engine devs can likely help you. game devs can help when there is some useful output i guess

(also adjusted topic)

[Beherith]

You failed at the part were you thought that you could use a regex on human written docs. Regex of that size is nearly write-only.

There are too many exceptions in the docs to allow this to work.

I apologize if this comment wasnt helpful, but it was about as helpful as your description of your error.

[abma]

https://springrts.com/wiki/Project_prop ... umentation

[PicassoCT]

Yes mock me... abma.. do it.. but i shall ride this dead horse, till the headcrab falls off dead

[Anarchid]

I think this is different from the idea of generating inline lua api documentation. One is required for humans to understand how the API works; the other is required to make Lua IDE's understand what API exists.

Both probably have to be coded into engine or at least the build setup, though.

[PicassoCT]

well, were it worked, it provides functionality at the moment- i hope abma delivers his part of the deal if i do the docu

https://github.com/PicassoCT/SpringLuaM ... ree/master