The opposite, ravioli classes or when it goes very badly: "class diarrhea" (my term, see below), can be worse. When breaking down a
business application, giant objects are usually a problem and something to avoid. When A) solving a complex and tightly integrated
problem that should be used as s
coupling.
sdw
On 4/25/11 2:50 PM, Adrian Crum wrote:
It would be interesting to see how an int wrapper would perform on Android.
-Adrian
On 4/25/2011 2:21 PM, Stephen Williams wrote:
Note that, as of Android 2.2's Dalvik at least, that Java5 enums are much much slower than using constants
Note that, as of Android 2.2's Dalvik at least, that Java5 enums are much much slower than using constants. For anything that gets
used frequently, and that might be used on Android, that is a problem. I wrote and optimized a SAX and DOM parser on Android.
While the JDK will optimize out most
On 3/30/11 12:02 AM, Ralph Goers wrote:
On Mar 29, 2011, at 7:40 PM, Stephen Williams wrote:
On 3/29/11 7:33 PM, Ralph Goers wrote:
On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
...
So, lesson learned: Don't use Maven! ;-)
No, the other one: make copies of your code through mul
On 3/29/11 7:33 PM, Ralph Goers wrote:
On Mar 29, 2011, at 7:24 PM, Stephen Williams wrote:
...
So, lesson learned: Don't use Maven! ;-)
No, the other one: make copies of your code through multiple means until it is
completely safe. I hadn't lost code (or any data through parano
On 3/29/11 6:36 PM, Gary Gregory wrote:
Wait! I'm not done or I'm loosing my marbles...
...
As I noticed this note, seems like a good point to interject a Maven war story:
I do not like Maven. I know I should, but it seems too complicated and too hard to use on complex projects. I may get ov
On 2/1/11 10:04 PM, Phil Steitz wrote:
...
Agreed. This is why we had a very flat hierarchy through version
2.0 of [math]. Where we are having trouble gaining consensus is how
to represent specializing context information in our exceptions and
what abstractions to use to represent the shallow h
On 2/1/11 4:31 PM, Stephen Williams wrote:
I know I've recently seen a great example of a library that started with generic exception classes then later changed to a
specific hierarchy. But I can't remember off hand which library it was...
There is some low level where you just w
On 1/28/11 3:14 PM, James Ring wrote:
Hey,
On Fri, Jan 28, 2011 at 3:00 PM, Stephen Williams wrote:
True, you shouldn't synchronize on any object that A) you want to change and
B) can only be changed by being replaced by a newly constructed object. If
Integer, for instance, had a s
Hah, just sent a reply stating just that. Thanks.
Stephen
On Fri, Jan 28, 2011 at 2:45 PM, Brent Worden wrote:
> Actually, funkyChanger will not work because you are effectively
> reassigning the argument. Since all arguments in Java are passed by
> value, the assignment is not realized by the
when more than a
few parameters are needed and they might change over time.
Stephen
On Fri, Jan 28, 2011 at 2:21 PM, James Ring wrote:
> Hey,
>
> On Fri, Jan 28, 2011 at 2:01 PM, Stephen Williams
> wrote:
> > All objects are passed as references in Java.
> > All fundamen
All objects are passed as references in Java.
All fundamental scalar types have Object wrapped versions.
An argument that is meant to be modified just needs to be an object
reference.
So, you can simply go from:
void funkyReader(int arg) { arg++; }
to:
void funkyChanger(Integer arg) { arg++; }
If
We are happy to publish the OpenEXI Apache Incubator proposal[1]. OpenEXI is a project to create open source implementations of the
W3C Efficient XML Interchange (EXI) specification in multiple languages, Java and C++ initially. EXI is an XML infoset equivalent
encoding in a highly compact bina
13 matches
Mail list logo
