meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 10 months |
| seen | Oct 15 '12 at 23:45 | |
| stats | profile views | 8 |
|
Sep 27 |
awarded | Fanatic |
|
Apr 8 |
awarded | Enthusiast |
|
Aug 12 |
awarded | Scholar |
|
Aug 12 |
accepted | Java class version specific naming conventions |
|
Aug 12 |
comment |
Java class version specific naming conventions Unfortunately, they are structurally different and need complex transformation. It's like bitmap and vector graphic. |
|
Aug 12 |
comment |
Java class version specific naming conventions They have many versions of data models that changes between releases. Some specific subsets of features are mixing together. No library support at all (e.g. no di, no codegen). This is history of 11 years software evolution :( . |
|
Aug 12 |
comment |
Java class version specific naming conventions This sounds good. I'll think about it. Though in the place that these versions come together, we need to use fully-qualified name for the references, right? |
|
Aug 12 |
awarded | Student |
|
Aug 12 |
awarded | Supporter |
|
Aug 12 |
asked | Java class version specific naming conventions |
