Why does Flash generate invalid class names for library items?

Question

I imported a bunch of bitmaps (PNGs).  The library symbol names all included the full file name and its extension.  When I check "export for actionscript" it generates a class name based on the symbol name, and it includes the ".png", even though that's invalid in a class name.
When I select multiple bitmaps and choose properties and export for actionscript, it has a note saying that classnames will be automatically generated for all items, but it does the same thing... including the ".png" in all the class names.  Is this a problem?  Wouldn't it save time if Flash would automatically strip the file extension from the instance name of bitmap library symbols when generating class names?

Answer 1

Thank you Nipun.  That is exactly the behavior I would expect, and I can confirm that in the trial of Flash CC it generates valid class names by removing the file extension.  For example, a file named "3ball.test.png" will receive an auto-generated class name of "_3ball_test", so it really does ensure the class name is valid (meeting AS3 class name syntax)
kglad, what I'm saying is that an image file name like "ball.png" is not a valid "class name", because it contains a period, which is reserved as a package delimiter.  I know the runtime can handle it as a valid "fully-qualified class name", but it's misleading because it's actually creating a class named "png" in package "ball", BUT it's understood that the auto-generated name is not supposed to be specifying any package, hence the misleading specification.  The class would have to be instantiated like this: "import ball.png; var bd:BitmapData = new png();" or "import ball.*; var bd:BitmapData = new png();"  You would also then have to import every single class individually and always use their fully qualified names, because you'd technically have a bunch of classes all named "png" inside a hundred different packages.  It's just not acceptable.
The other problem that occurred in CS6 is if you loaded a bunch of files whose names started with numbers, then when you select them all, choose properties, and use the batch properties window to export them for actionscript, I noticed that such images would be auto-assigned generic names like "Class4" as it would realize the default auto-generated class name would be invalid.  This problem has been fixed beautifully in Flash CC.
Nipun, it would actually be very helpful to have a little more control over the class naming conventions.  For example, if I wanted all my BitmapData classes to exist in an "images" folder or package, it would be helpful if in the batch properties window I could specify a package name for all the auto-generated class names.  When importing hundreds of images, it's very tedius to have to edit them individually and I don't always have time to write a JSFL script.  There's room in that window to add a text field for a package name.  Thanks!