fbfrog header translator

[speedfixer]

Did the second branch get far enough along to be useful? (60 commits ahead/4 commits behind master - philosophical shift?)
Were there features that would/should be rolled into the master?

An immediate project of mine is using the Raspberry PI for several modest tasks in a much larger network and I want to write more directly to the core of the system in places. FB so far has been excellent for this, but there are so many base libraries to address.

I'm still learning fbfrog (so I can avoid learning more C). Zero interest in Python.

david

[dkl]

No, it's unfinished, so not really useful. It's a mix of two ideas -
1) using libclang in fbfrog instead of a custom parser. Good, except it can't parse #define bodies, so it still needs some custom parsing for that.
2) making a "just-in-time bindgen" (for 1 target only instead of all targets). There is some better code at https://github.com/dkl/fbc/compare/master...dkl:bindgen for this approach. See also viewtopic.php?f=8&t=26175

[paul doe]

No, it's unfinished, so not really useful. It's a mix of two ideas - ...

Mmm? I beg to differ. The amount of work it can save me is substantial and, very frequently, it only leaves me with trivial stuff to deal with. Makes porting some stuff a breeze. Thank you so much for this little 'useless' tool ;)

[speedfixer]

Is there a provision to comment a line in the '*.fbfrog' or '*.options' file?

This would be helpful.
One favorite option file can be copied across many translates with 'touchups' for specific files without having to search down that one single file that had the exception you need again.

david

[dkl]

Yea it allows # comments. The *.fbfrog files can also include others recursively, which can be useful to extract and reuse common parts.

[speedfixer]

Thanks.

Are you pretty much done with this?

I'm working on rPI stuff right now.
Translates aren't too hard; I get them to work without that much difficulty.

I would have sets of questions and more if you were to be active on this.

If not, it certainly works well enough to save so much time. (With fbc so fast, trial and error makes everything so simple.)
Thank you for this program!


One question:
How should one deal with an FB reserved keyword defined in another library?

At the moment, the word is shell.


david

[dkl]

Yea go ahead, if I can help out a bit that's fine for me. I got no plans to make any big improvements though.

For symbol naming conflicts usually the solution is to do something like declare function shell_ alias "shell" .... There is an fbfrog option for that, -rename_ shell, or -renameproc shell foo if you prefer another name than shell_.

[speedfixer]

Thank you.

No more for now.