|
From: Lomwel, Alexander-v. <ale...@mi...> - 2003-11-28 13:15:49
|
I have to get back on this: flex 2.5.4-2 uploaded to master =B7 To: Debian Developer Changes <deb...@li... <mailto:deb...@li...>>=20 =B7 Subject: flex 2.5.4-2 uploaded to master=20 =B7 From: Santiago Vila Doncel <sa...@un... <mailto:sa...@un...>>= =20 =B7 Date: Thu, 13 Mar 1997 10:10:19 +0100 (CET)=20 =B7 Cc: 778...@bu... <mailto:778...@bu...>=20 It's also available in <ftp://ftp.unex.es/pub/linux/debian/flex> -----BEGIN PGP SIGNED MESSAGE----- Format: 1.5 Date: Thu, 13 Mar 1997 09:44:28 +0100 Source: flex Binary: flex Architecture: source i386 Version: 2.5.4-2 Distribution: unstable Urgency: low Maintainer: Santiago Vila <sa...@ct...> Description:=20 =20flex - A fast lexical analyzer generator. Changes:=20 =20flex (2.5.4-2) unstable; urgency=3Dlow =20. =20 * libfl.a stripped using strip -g, using a modified debstd which =20 is included in the Debian source package. Files:=20 =2093bdcf2bc4e8a695f19119e0711aace4 605 devel standard flex_2.5.4-2.dsc =207dc533b8f6a4902398fbfeedc54917c5 8272 devel standard flex_2.5.4-2.diff= .gz =20c3e751619d5855964efce69471780c67 149474 devel standard flex_2.5.4-2_i386.deb -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: latin1 iQCVAgUBMyfBSCqK7IlOjMLFAQGdJwQArATG+7QFD5yw5zhi8kLuLyjBUrJfoCig 6E8mYwsoTvtuLsF3tHTcCXIh8L6REFGBO2yd4DRgPbpcm+tX8t0nRPpSxSBHR7uZ r5/ogiPot9nEJl7nITw69Z6M6nleSNvq/iS1ntXZvnMIKXCkdPIJ+pIqvy9z1xsJ qIA2nCHUWRY=3D =3D/tfq -----END PGP SIGNATURE----- > -----Original Message----- > From: Lomwel, Alexander-van=20 > Sent: vrijdag 28 november 2003 13:31 > To: 'pla...@li...' > Subject: RE: [Plantool-developer] Flex errors and warnings >=20 >=20 > Reinout; > has a good approach here. Lets stick to it.=20 >=20 > The root couse analysis is flawed however. flex creates from=20 > the tokeniser > files a flex.c file. Herein some defines steer the compilation like > YY_NO_UNPUT, and some useless cose is automaticly inserted=20 > like the command > yy_flex_realloc. (read BUG) These result in compiler warnings, which I > sought to surpress, but which cause problems with older=20 > versions of flex, > which don't seem to have the BUG, but also not know what to=20 > do with the > define. >=20 > greetings; > Alexander >=20 > PS Overal conclusion: > we live with the warnings. > Get rid of #define YY_NO_UNPUT, and the function CatchSillyWarnings(). > As MvR already did for the most part. >=20 >=20 >=20 > > -----Original Message----- > > From: Reinout van Rees [mailto:re...@va...] > > Sent: vrijdag 28 november 2003 13:22 > > To: pla...@li... > > Subject: Re: [Plantool-developer] Flex errors and warnings > >=20 > >=20 > > On Fri, 28 Nov 2003, Maurits van Rees wrote: > >=20 > > > Lomwel, Alexander-van wrote: > > > > Hello Maurits; > > > > > > > > The lowest flex version I use is: > > > > flex version 2.5.4 > > > > > > > > please upgrade. > > > > > > I am now updating my Debian system. flex 2.5.31 (which I=20 > > now have) is > > > the newest I can find... :( > >=20 > > It would be nice to use debian-stable as a kind of minimum.=20 > Upgrading > > something like flex beyond what's normally available also=20 > means adding > > a new gcc, a new libc and basically replacing half your system... > >=20 > > Unless there is something *really* wrong with the old version or if > > something big is missing: make sure it compiles/parses/whatever with > > the older version. From what I saw till now it was mostly syntax > > errors which the newer one allowed, undefined variables in=20 > C for which > > the declaration had to be moved upwards, etc. Hardly too > > inconveniencing. > >=20 > > And if something slips through, Maurits (or me) catches it. > >=20 > > Reinout > >=20 > > --=20 > > Reinout van Rees - re...@va... > > http://vanrees.org/ > > "I bet that's a real nice ship now that the rats have left." > >=20 > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > Plantool-developer mailing list > > Pla...@li... > > https://lists.sourceforge.net/lists/listinfo/plantool-developer > >=20 >=20 > Disclaimer Ministerie van Buitenlandse Zaken: > De informatie verzonden met dit e-mailbericht is uitsluitend=20 > bestemd voor de > geadresseerde. Gebruik door onbevoegden, openbaarmaking of=20 > vermenigvuldiging is > verboden. De afzender is niet aansprakelijk in geval van=20 > onjuiste overbrenging van > het e-mailbericht en/of bij ontijdige ontvangst daarvan. >=20 > Disclaimer Ministry of Foreign Affairs of the Netherlands: > The information transmitted is intended only for the person=20 > or entity to whom or which > it is addressed. Unauthorised use, disclosure or copying is=20 > strictly prohibited. The > sender accepts no liability for the improper transmission of=20 > this communication nor for any > delay in its receipt. >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Plantool-developer mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/plantool-developer >=20 Disclaimer Ministerie van Buitenlandse Zaken: De informatie verzonden met dit e-mailbericht is uitsluitend bestemd voor= =20de geadresseerde. Gebruik door onbevoegden, openbaarmaking of vermenigvuldig= ing is verboden. De afzender is niet aansprakelijk in geval van onjuiste overbre= nging van het e-mailbericht en/of bij ontijdige ontvangst daarvan. Disclaimer Ministry of Foreign Affairs of the Netherlands: The information transmitted is intended only for the person or entity to = whom or which it is addressed. Unauthorised use, disclosure or copying is strictly proh= ibited. The sender accepts no liability for the improper transmission of this communi= cation nor for any delay in its receipt. |