Am I missing something in my java config, or are there really no error/warning messages in the current 4.6b11?

public-beta-compiler-errors

Some other people on the list were having a similar problem. We need 

On Jul 25, 2006, at 11:20 AM, jbmaxwell wrote:

> Am I missing something in my java config, or are there really no 

> error/warning messages in the current 4.6b11?

What is your setup?
Some other people on the list were having a similar problem. We need  
to track this down.
Topher

>
> Am I missing something in my java config, or are there really no  
> error/warning messages in the current 4.6b11?
>
> J.


My topic heading isn't that clear. It's just that I get no notification of what went wrong during compilation... just to be clear.

Anyway, it's a MacBook 1.83, only 512 MB ram at this point. MaxMSP 4.6b11. OS X 10.4.7, with all the latest updates. This does include a new release (release 4?) of Java 5.0. Could there be an issue there?...

There is something weird going on with the mactel.

I don't have access to one right now but am

trying to see what may have changed in the output.

If you compile from the command line could you send

me the error output so I can see how it is formatted.

Perhaps it changed? I dont think so though.

On Jul 25, 2006, at 12:28 PM, jbmaxwell wrote:

> My topic heading isn't that clear. It's just that I get no 

> notification of what went wrong during compilation... just to be 

> Anyway, it's a MacBook 1.83, only 512 MB ram at this point. MaxMSP 

> 4.6b11. OS X 10.4.7, with all the latest updates. This does include 

> a new release (release 4?) of Java 5.0. Could there be an issue 

There is something weird going on with the mactel.
I don't have access to one right now but am
trying to see what may have changed in the output.
If you compile from the command line could you send
me the error output so I can see how it is formatted.
Perhaps it changed? I dont think so though.
Topher

>
> Hey Toph,
>
> My topic heading isn't that clear. It's just that I get no  
> notification of what went wrong during compilation... just to be  
> clear.
>
> Anyway, it's a MacBook 1.83, only 512 MB ram at this point. MaxMSP  
> 4.6b11. OS X 10.4.7, with all the latest updates. This does include  
> a new release (release 4?) of Java 5.0. Could there be an issue  
> there?...
>
> J.


well, I always just use the built-in text editor/compiler. Here's a screenshot, but I doubt it will be very informative. Just says compilation failed, nothing more.

[EDIT] hmm.. couldn't get it to attach the screenshot. Anyway, it just tells me complition failed...

Well, I just realized that I'm not supposed to be able to run the beta without an authorized MaxMSP 4.5 installed... It does run on my new MacBook, though. Anyway, I've submitted an authorization request, so maybe that will have some effect(?)

The other thing I noticed is that ArrayList() is taking ints. I've just tried:

...and it appears to work. That isn't right, is it? Isn't ArrayList only supposed to take objects, not primitives? Could this be a 4.6 bug; maybe it's not actually taking my int input as an int, but is rather converting it to an Atom?

We'll see if things change once authorized (though I don't know why they would).

public void add(int i)
   {
   thisArrayList.add(i);
   }

dunno, just curious.
We'll see if things change once authorized (though I don't know why they would).

duh... investigating my little "problem" further, it looks like this is probably just the autoboxing added in J2SE 5.0/1.5. 

It is probably worth note, though, that 4.6b11 does appear to work in demo mode, without 4.5 installed.

duh... investigating my little "problem" further, it looks like this is probably just the autoboxing added in J2SE 5.0/1.5. 
Sorry for the false alarm. :-

On 28 Jul 2006, at 18:48, jbmaxwell wrote:

> duh... investigating my little "problem" further, it looks like 

> this is probably just the autoboxing added in J2SE 5.0/1.5.

If you're using Eclipse, you can ask it to flag these conversions.

nick rothwell -- composition, systems, performance -- 

> duh... investigating my little "problem" further, it looks like  
> this is probably just the autoboxing added in J2SE 5.0/1.5.

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


Is the autoboxing relatively efficient, btw? It could come in very handy.

On 28 Jul 2006, at 19:27, jbmaxwell wrote:

> Is the autoboxing relatively efficient, btw? It could come in very 

Don't know; I assume it's pretty much equivalent to doing it 

manually. But since it's automatic, I guess there's always the risk 

that you end up making more use of it than you'd like.

In any case: I personally don't worry about it, since at worst it's a 

slight performance hit linear with the number of occurrences, and 

there are better ways to apply one's optimisation effort.

> Is the autoboxing relatively efficient, btw? It could come in very  
> handy.

Don't know; I assume it's pretty much equivalent to doing it  
manually. But since it's automatic, I guess there's always the risk  
that you end up making more use of it than you'd like.

In any case: I personally don't worry about it, since at worst it's a  
slight performance hit linear with the number of occurrences, and  
there are better ways to apply one's optimisation effort.

I've just done the 4.6.1 update (finally), but I still get no error information from the compiler, just the notification that the build failed.

Is it possible that this is just my system? I do have ftm installed, btw... in case it makes a difference.

Okay, am I the only one who doesn't get any sort of error messages from the 4.6.2 java compiler? "build failed"... but that's about it.

You're not alone: this is a known bug that has caused us some grief.

We're waiting on a fix from Apple. Sorry, no idea when it will

happen, or when/if we'll figure out another way to get the error

1. compile manually from the terminal, or

> Okay, am I the only one who doesn't get any sort of error messages from the 4.6.2 java compiler? "build failed"... but that's about it.

You're not alone: this is a known bug that has caused us some grief.
We're waiting on a fix from Apple.  Sorry, no idea when it will
happen, or when/if we'll figure out another way to get the error
messages back.

1. compile manually from the terminal, or
2. use an IDE such as Eclipse

On 9/28/06, jbmaxwell  wrote:
>
> Okay, am I the only one who doesn't get any sort of error messages from the 4.6.2 java compiler? "build failed"... but that's about it.
>
> J.
>


I hadn't heard anything for a while, and with another service update released (4.6.2) I thought maybe my system was to blame.

Anyway, I work on my G5 most of the time, but it would be nice to get out of the studio occasionally (especially for programming, which doesn't need the extra gear). Would somebody mind posting an announcement of some kind once this particular problem is fixed?

public beta compiler errors?