AW: [Htmlparser-developer] Latest code Problems

[Holger S. <Hol...@xt...>]

Hi!

...stupid question: Do we really need to still support JDK 1.1?

I know that relying on the new features of 1.4 would blow many current =
apps, so we should not do this for the time being.
But the integration of e.g. the Collections framework introduced in JDK =
1.2 (which is a long time ago) into HTMLParser should be possible and =
done. =20

So to add my opinion to the poll: I would like to drop support for JDK =
1.1.=20

Holger

-----Urspr=FCngliche Nachricht-----
Von: Derrick Oswald [mailto:Der...@ro...]
Gesendet: Mittwoch, 8. Januar 2003 14:11
An: htm...@li...
Betreff: Re: [Htmlparser-developer] Latest code Problems

<snip>
> =20
> [2] HTMLLinkBeanInfo and HTMLTextBeanInfo dont compile. Are you=20
> relying on something in JDK 1.4 ? Bytway, htmlparser is JDK 1.1=20
> compliant. I am not sure if that should change, but then again, it=20
> really depends on the users of the parser.

1.1 compatibility is news to me. This has probably been broken for a=20
while (see ArrayList in ChainedException and Iterator in Translate).
Version 1.1 is usually mandated by old browser JVM support, or legacy=20
(unsupported)  operating systems. I don't think it's an issue here since =

it's not running as an applet. The use of the Vector class (required=20
under JDK 1.1) is a bit of a performance hit since the class is=20
synchronized.

For now just delete those 'BeanInfo' files and it should compile OK, but =

I'll see if I can fix it for you, and then a decision can be made about=20
continuing 1.1 support.

</snip>

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See!
http://www.vasoftware.com
_______________________________________________
Htmlparser-developer mailing list
Htm...@li...
https://lists.sourceforge.net/lists/listinfo/htmlparser-developer