[armedbear-ticket] [armedbear] #34: adjust generated '*.cls' filenames

[armedbear]

#34: adjust generated '*.cls' filenames
-------------------------+--------------------------------------------------
  Reporter:  mevenson    |       Owner:  somebody
      Type:  defect      |      Status:  new     
  Priority:  major       |   Milestone:          
 Component:  component1  |     Version:          
Resolution:              |    Keywords:          
-------------------------+--------------------------------------------------

Comment(by dmiles):

 coerce-666.cls  -> coerce_666.class

 I can only speculate the reasons for using .cls:

 The use of .cls was maybe we were not sure if ABCL was going to do new
 stuff with the .class file format. - But it didn't.

 The use of .cls keeps the (parent/system) classloaders from making
 assumptions that they can autoload these classes on their own (at the
 wrong time).

 However I believe niether of the two issues would come up.



 I have a special debugging plugin I use under eclipse that lets me inject
 and reinterpret and trace verify errors that is usefull in
 debugging/decompiling the .class files .. I had to extend this debugger to
 handle .cls files.. This is available to me as a hack.. But if I wasnt me,
 and was using  Jode/JADClipse debugger plugins I would have issues.

 Renaming the these to .class files has nothing to do with *just getting* a
 debugger working.  But opens us up our autoload framework to leverage more
 types of compiler outputs  and allows precompiler and bytecode loading
 systems from other types of JVMs on the right page to our class files.

-- 
Ticket URL: <http://127.0.0.1:8000/armedbear/ticket/34#comment:1>
armedbear <http://common-lisp.net/project/armedbear>
armedbear