[Asunit-users] Re: [osflash] ASUnit, MTASC, and Me

[Luke B. <lb...@gm...>]

Hey Don,

Thanks for the reply. I definitely appreciate your patience in getting
through this. If you wouldn't mind, could you please let me know
exactly which files were still complaining about the unused import
statements?

It would really help us get AsUnit to be less painful for everyone!


Thanks,


Luke Bayes
www.asunit.com



On 7/3/05, Don Petersen <dpe...@cr...> wrote:
> Luke,
>=20
> I was writing my follow-up email as you sent this.  You're definitely
> right about Object not being treated as dynamic.  But to summarize my
> other email, as far as I can tell it is only an issue when compiling
> through Flashout, and only on Linux.  I'd love to see if anybody else
> has the same issue with a similar setup, or if I'm just "lucky"!
>=20
> I did go ahead and modify ASUnit as you directed below(and in a few
> other places, as that issue pops up elsewhere).  A couple minutes of
> modification and now I'm compiling OK in Flashout.  Given the crazy set
> up circumstances that have to appear for this to happen, I definitely
> wouldn't call it an issue with ASUnit.  I'll leave my copy modified for
> the weekend and see if Eugene or anybody else has the same issue, or any
> ideas why it might be occuring.
>=20
> As far as immense frustration, it was hardly that bad.  I'm just excited
> to be able to use this cool piece of software now!  Unit Testing, here I
> come...
>=20
> Don Petersen
>=20
>=20
> > I just caught this post and it looks like there are a couple bugs in
> > AsUnit related to the latest MTASC compiler.
> >
> > I just fixed and checked in the Test.as warning in the cvs sources, if
> > it bothers you (as much as it would bother me!), feel free to remove
> > the import statement from that file in your local build, it will be
> > fixed in the next release.
> >
> > As far as the error goes...
> >
> > /home/dpetersen/workspace/test_ut/src/com/asunit/framework/Assert.as:98=
:
> > characters 5-22 : type error Object have no field equals
> >
> > It loos like MTASC is not treating the Object object as a "dynamic"
> > class in this case.
> >
> > I don't have FAME all set up on this system right now, so I can't
> > really test a fix. Could someone take a look at line 98 of the
> > com.asunit.framework.Assert class?
> >
> > It looks to me like this statement:
> >
> > if(assertion1.equals !=3D undefined) {
> >         addTestResult(String(msg), "assertEquals",
> > assertion1.equals(assertion2));
> > } else if(assertion2.equals !=3D undefined) {
> >         addTestResult(String(msg), "assertEquals",
> > assertion2.equals(assertion1));
> > } else {
> >         addTestResult(String(msg), "assertEquals", assertion1 =3D=3D=3D
> > assertion2);
> > }
> >
> > Might need to change to:
> >
> > if(assertion1["equals"] !=3D undefined) {
> >         addTestResult(String(msg), "assertEquals",
> > assertion1["equals"](assertion2));
> > } else if(assertion2["equals"] !=3D undefined) {
> >         addTestResult(String(msg), "assertEquals",
> > assertion2["equals"](assertion1));
> > } else {
> >         addTestResult(String(msg), "assertEquals", assertion1 =3D=3D=3D
> > assertion2);
> > }
> >
> > Do the brackets work in MTASC?
> >
> > Could you try pasting this into your local build and let me know if it
> > works?
> >
> > Thanks for the heads up and sorry for the immense frustration!
>=20
> _______________________________________________
> osflash mailing list
> os...@os...
> http://osflash.org/mailman/listinfo/osflash_osflash.org
>