Namespace arcane not found again
Makc
Some code of mine throws this error with current trunk.
On Fri, May 23, 2008 at 2:44 AM, Rob Bateman <rob.b...@gmail.com> wrote:
> Hey Ralph
>
> I've seen this before and i've no idea why it keep occuring. It's a phantom
> bug that only seems to surface every once in a while... possibly to the
> phases of the moon ;)
>
> various way to fix it have been noted: try typing the full import to arcane
> (presume you've already tried this). try clearing your aso files in cs3 (i
> assume your using cs3 as i've not heard of this occurring anywhere else),
> try inserting a return character before the namespace reference (my personal
> favorite :D) - these thing have all 'apparantly' fixed the compile error in
> the past.
The above tricks were not helpful.
The funny part is that I have complaints about Sphere class that I
neither use nor import explicitly. Any way, following change have
(temporary ?) solved this for me:
package away3d.primitives
{
import away3d.core.*;
import away3d.core.base.*;
import away3d.core.utils.*;
/**
* Creates a 3d sphere primitive.
*/
public class Sphere extends AbstractPrimitive
{
use namespace arcane
...
to
package away3d.primitives
{
import away3d.core.*;
import away3d.core.base.*;
import away3d.core.utils.*;
/**
* Creates a 3d sphere primitive.
*/
use namespace arcane
public class Sphere extends AbstractPrimitive
{
...
I find no documented reference to this problem in the adobe
> bugtracker which is strange - clearly the code is correct but something is
> going wrong in the compiler execution. might post one myself
>
> let me know how you get on - i'd like to see the back of this if possible
>
>
> cheers
>
> Rob
>
>
> On Thu, May 22, 2008 at 1:33 PM, Ralph B <ra...@satprof.com> wrote:
>>
>> Rob & team,
>> I am stumped by a recurring compile error, typically:
>>
>> AbstractShader.as, Line 24 1004: Namespace was not found or is not a
>> compile-time constant.
>>
>> It seems to be triggered by any call to Cast.trycolor() from a class
>> that I have created that extends Object3DContainer where there are
>> declarations of materials. However it is maddeningly inconsistent:
>> e.g. I comment out everything except a few lines that trigger the
>> error, comment them out and the compile error stops, then uncomment
>> them and the error does not come back!
>>
>> I do have import away3d.core.* in every class that I am using. I
>> noticed however that in many of the away3D primitives, arcane.as is
>> not explicitly imported so was wondering that may have something to do
>> with it.
>>
>> I have been chasing my tail on this so any suggestions would be
>> gratefully received.
>>
>> Ralph
>
>
>
> --
> Rob Bateman
> Flash Development & Consultancy
>
> rob.b...@gmail.com
> www.infiniteturtles.co.uk
> www.away3d.com