From the SWIG manual: -------8<--------------- SWIG 1.3.28 introduces the new -autorename command line parameter. When this parameter is specified, SWIG will automatically change constant, class and method names to conform with the standard Ruby naming conventions. ... To disable renaming use the -noautorename command line option. Since this change significantly changes the wrapper code generated by SWIG, it is turned off by default in SWIG 1.3.28. However, it is planned to become the default option in future releases. -------8<--------------- I haven''t tested how this does renaming but it may free us from parts of our rename script. Also, we will, at the least, have to use the -noautorename flag if we don''t wish to use SWIG''s renamer. Thoughts? Roy
On Mon, 2006-04-17 at 00:42 -0400, Roy Sutton wrote:> I haven''t tested how this does renaming but it may free us from parts of > our rename script. Also, we will, at the least, have to use the > -noautorename flag if we don''t wish to use SWIG''s renamer. Thoughts?Hopefully their rules match ours. If so, it would probably work for us, and we could get rid of our renamer.rb tool. I can''t think of any special cases that would hurt us, but I guess we''ll have to try it to know for sure. Kevin
Kevin Smith wrote:> On Mon, 2006-04-17 at 00:42 -0400, Roy Sutton wrote: > >> I haven''t tested how this does renaming but it may free us from parts of >> our rename script. Also, we will, at the least, have to use the >> -noautorename flag if we don''t wish to use SWIG''s renamer. Thoughts? >> > > Hopefully their rules match ours. If so, it would probably work for us, > and we could get rid of our renamer.rb tool. I can''t think of any > special cases that would hurt us, but I guess we''ll have to try it to > know for sure. >I have been working with their renamer a bit. It seems to do what ours do (at least for the cases I''ve tested so far). I suppose I could write some tests to verify! I was using it in conjunction with %predicate and %alias, which work pretty well. Roy