04730: pleiads & clones: pleiadbl should be pleiadsbl and pleiadce should be pleiadsce

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
04730	Misc.	Typo	Always	Mar 13, 2012, 19:31	Mar 13, 2012, 20:04

Tester	moa	View Status	Public	Platform	MAME (Unofficial Binary)
Assigned To		Resolution	No change required	OS	Windows Vista/7 (64-bit)
Status [?]	Closed			Driver	phoenix/phoenix.cpp
Version	0.145u4	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	04730: pleiads & clones: pleiadbl should be pleiadsbl and pleiadce should be pleiadsce
Description	According to the recent naming convention (clone=parent+ext) Pleiads (bootleg) -> pleiadsbl Pleiads (Century) ->pleiadsce If it's correct I might submit others... Thank you
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	pleiads & clones

Attached Files

No.08341 Tafoid Administrator Mar 13, 2012, 20:04	Changing long established set names is usually reserved for those who work on the drivers first-hand or you are doing other emulation related work in that driver. Such 8 character clone names that 'could' be changed are not considered to be a bug, in the strictest sense. They really are a non-issue and not worth even filling a bug report about them. I am not stating that you cannot send in a .diff to MAMEDEV to cover some setname changes - it is just that it is usually, as I mentioned, a perk of working on a driver's emulation in some way a developer has a say how to best access a game via their chosen shortname. No change is needed here. Closing.

No.08341

Tafoid

Administrator

Mar 13, 2012, 20:04

Changing long established set names is usually reserved for those who work on the drivers first-hand or you are doing other emulation related work in that driver. Such 8 character clone names that 'could' be changed are not considered to be a bug, in the strictest sense. They really are a non-issue and not worth even filling a bug report about them.

I am not stating that you cannot send in a .diff to MAMEDEV to cover some setname changes - it is just that it is usually, as I mentioned, a perk of working on a driver's emulation in some way a developer has a say how to best access a game via their chosen shortname.

No change is needed here.
Closing.