At Google I/O and in the forums, it has been clear that if you need
optimal performance, you must avoid memory allocation inside tight
loops. I'm curious about the best way to handle this in my use-case,
which I think must be fairly common. I need to access at most n
objects of type MyObject, I
gt;
> > thanks for the response,
> > -Jey
>
> > On Aug 28, 10:58 am, Brad Larson <[EMAIL PROTECTED]> wrote:
>
> > > I was able to get it working in Eclipse by setting my project to
> > > include the source from the library project. I was never able to
ey <[EMAIL PROTECTED]> wrote:
> On Aug 11, 11:48 am, Brad Larson <[EMAIL PROTECTED]> wrote:
>
> > I took the auto-generated build.xml
> > and modified it to pass the .jar files to dx. Everything works fine
>
> Can you share the bits of the build.xml ?
&
I'm using windows, although I have access to a linux box if that is
needed
On Aug 19, 5:27 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Which OS are you using?
>
> On Tue, Aug 19, 2008 at 3:15 PM, Brad Larson <[EMAIL PROTECTED]> wrote:
>
> >
ectly...
>
> On Tue, Aug 19, 2008 at 2:26 PM, Brad Larson <[EMAIL PROTECTED]> wrote:
>
> > Has the sqlite3 command line tool been removed from 0.9beta? I
> > haven't been able to find anything in the documentation, but I do get
> > sqlite3: not found from
Has the sqlite3 command line tool been removed from 0.9beta? I
haven't been able to find anything in the documentation, but I do get
sqlite3: not found from the shell. This was a useful debug tool... if
it has been removed, is there anything to replace it?
Thanks,
Brad
--~--~-~--~~-
6 matches
Mail list logo
