JNAerator doesn't parse files that don't contain ".h" suffix in the name

[GoogleCodeExporter]

What steps will reproduce the problem?
1.run jnaerator on c/c++ header file that doesn't have ".h" extension
2.
3.

What is the expected output? What do you see instead?
Parsing of the file. Generated output. Without extension I receive this:
"Now parsing 0 text blocks"

If i copy the file to contain an extension then I receive this:
"Now parsing 27 text blocks"

What version of the product are you using? On what operating system?
jnaerator-v0.9-b614.jar ,MacOSX 10.5.8

Please provide any additional information below.
I'm am trying to wrap a third party lib using jnaerator. The library is 
composed of many header 
files and many sub libraries. The issue I have is that the headers don't 
contain the ".h" suffix in 
the name. In fact, they have no suffix. Is it possible to add a flag/option to 
parse all files in a 
directory no matter the suffix?

Original issue reported on code.google.com by gbivi...@gmail.com on 31 Aug 2009 at 4:33

[GoogleCodeExporter]

Hi, 

Thanks for the bug report !

Indeed, the only valid extensions right now are .h, .hxx, .hpp.
This was meant to limit the files listed recursively when a directory is listed 
as 
input, but it shouldn't affect files given directly in command line (+ we 
should add an 
option with allowed extensions for recursive scans).

Original comment by olivier.chafik@gmail.com on 31 Aug 2009 at 8:33

• Changed state: Accepted

[GoogleCodeExporter]

Hi,

I've checked in a fix and updated the latest SVN JAR (build 616).
Could you please confirm that this is indeed fixed ? (feel free to update the 
bug status)

Best regards
--
Olivier

Original comment by olivier.chafik@gmail.com on 31 Aug 2009 at 6:39

• Changed state: Fixed

[GoogleCodeExporter]

Hey!!
Works for me! 
Thanks for the fast turn around!

Original comment by gbivi...@gmail.com on 31 Aug 2009 at 7:21

[GoogleCodeExporter]

You're welcome :-)

Well, it actually looks I've broken the parsing of regular .h files... so I 
recommend to update to the new SVN latest 
version (build 617).

Cheers 

Original comment by olivier.chafik@gmail.com on 31 Aug 2009 at 10:07