fd2pragma case sensitivity

phx · 09 October 2016, 12:27

By receiving a bug report I noticed that fd2pragma always creates its proto-, inline-, pragma- file names with lower-case letters, which is a problem in a few cases.

For example for Warp3D and Picasso96API, which use upper-case letters in their name. This leads to the problem that, when cross-compiling under a Unix-like file system, you cannot include clib/warp3d_protos.h, because it's called Warp3D_protos.h in the official SDK!

Also the FD-file, which fd2pragma uses as input, is called Warp3D.fd. And the base name of the FD-file is usually taken to construct the file names of all the other files.

I think it is a bug in fd2pragma, to force this base name into lower case. But, on the other hand, there may be many sources out there, which will need fixing after my fd2pragma-modification, because "#include <proto/warp3d.h>" no longer works in future (vbcc) releases under Unix.

So I'm a bit anxious to commit this fix now, for a problem which existed since 20 years. Any suggestions from the community?

alkis · 09 October 2016, 13:08

What if you created both? (lower cased and the non-lowered case)

phx · 09 October 2016, 13:25

clib/Warp3D_protos.h is not created by fd2pragma. It comes from the official Warp3D SDK.

I could create a proto/warp3d.h, which includes clib/warp3d_protos.h and a proto/Warp3D.h, which includes clib/Warp3D_protos.h. But why creating the first one, when it doesn't work under Unix anyway?

09 October 2016, 12:27	#1
phx Natteravn Join Date: Nov 2009 Location: Herford / Germany Posts: 2,496	fd2pragma case sensitivity By receiving a bug report I noticed that fd2pragma always creates its proto-, inline-, pragma- file names with lower-case letters, which is a problem in a few cases. For example for Warp3D and Picasso96API, which use upper-case letters in their name. This leads to the problem that, when cross-compiling under a Unix-like file system, you cannot include clib/warp3d_protos.h, because it's called Warp3D_protos.h in the official SDK! Also the FD-file, which fd2pragma uses as input, is called Warp3D.fd. And the base name of the FD-file is usually taken to construct the file names of all the other files. I think it is a bug in fd2pragma, to force this base name into lower case. But, on the other hand, there may be many sources out there, which will need fixing after my fd2pragma-modification, because "#include <proto/warp3d.h>" no longer works in future (vbcc) releases under Unix. So I'm a bit anxious to commit this fix now, for a problem which existed since 20 years. Any suggestions from the community?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE & Mouse sensitivity in Ubuntu	zardoz	support.WinUAE	3	07 December 2013 22:02
Mouse mat to lower optical mouse sensitivity?	Bamiga2002	support.Hardware	7	22 March 2013 07:35
mouse sensitivity problem on analogue joystick	fil	support.WinUAE	4	05 September 2011 19:53
changing mouse sensitivity	boing_1000	support.WinUAE	5	07 September 2006 18:44
Wanted! CD32 Case and A1200 Case!	ElectroBlaster	MarketPlace	0	08 December 2002 18:28

09 October 2016, 13:08	#2
alkis Registered User Join Date: Dec 2010 Location: Athens/Greece Age: 53 Posts: 719	What if you created both? (lower cased and the non-lowered case)

09 October 2016, 13:25	#3
phx Natteravn Join Date: Nov 2009 Location: Herford / Germany Posts: 2,496	clib/Warp3D_protos.h is not created by fd2pragma. It comes from the official Warp3D SDK. I could create a proto/warp3d.h, which includes clib/warp3d_protos.h and a proto/Warp3D.h, which includes clib/Warp3D_protos.h. But why creating the first one, when it doesn't work under Unix anyway?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)