Un-nesting Classes
20 views
Skip to first unread message
Stuart Gill
Dec 9, 2011, 8:59:06 PM12/9/11
to sfntly-eng, sfntly...@googlegroups.com
There are a number of nested classes within some of the table classes
(e.g. GlyphTable and CMapTable) which cause those class files to be
very large and a bit cumbersome. I will be un-nesting these and moving
them to sit beside the class they are being extracted from. So, for
example, the CMapFormat4 class currently is nested within the
CMapTable class. When the change is complete the CMapFormat4 class
will be in a file in the same package as the CMapTable class. This
change will affect many of the nested classes in GlyphTable and
CMapTable and possible some other tables.
(e.g. GlyphTable and CMapTable) which cause those class files to be
very large and a bit cumbersome. I will be un-nesting these and moving
them to sit beside the class they are being extracted from. So, for
example, the CMapFormat4 class currently is nested within the
CMapTable class. When the change is complete the CMapFormat4 class
will be in a file in the same package as the CMapTable class. This
change will affect many of the nested classes in GlyphTable and
CMapTable and possible some other tables.
This may cause some breakages in code which imports those classes. The
change will simply be a quick auto-fix in Eclipse for your code to
"organize imports". The change will likely be submitted to the svn
repository in the first week of January.
Stuart
Stuart Gill
Jan 12, 2012, 6:01:41 PM1/12/12
to sfntly-users
The un-nesting work has been checked in with r124.
Stuart
Stuart
Reply all
Reply to author
Forward
0 new messages