chuck Fri, 05 Jan 2007 14:21:38 -0800 Renamed "ShowStoppers" to "ShowStoppersThreeOh". New page: http://wiki.horde.org/ShowStoppersThreeOh -- To unsubscribe, mail: cvs-unsubscribe@lists.horde.org

jan Fri, 05 Jan 2007 02:10:49 -0800 Modified page: http://wiki.horde.org/ShowStoppers New Revision: 1.29 Change log: Note version @@ -1,5 +1,5 @@ -+ Release Show Stoppers ++ Horde 3.0 Release Show Stoppers ++ All modules * Convert remaining conf.php.dist files to conf.xml files (DONE). -- To unsubscribe, mail: cvs-unsubscribe@lists.horde.org

... problems such as aircraft weight and range have apparently been solved, questions about the release of the computer source code that makes the aircraft so unique have emerged as a potential showstopper for international clients. The source code in question refers to the millions of lines of computer code that allow this 21st-century aircraft to fly and to fight. Without complete access to ...

... Now nvsvc32.exe is definitely in \windows\system32\, so it must be some other file. However, I ran the install with filemon running, and I can't see anything that would be a showstopper. Any ideas on what may be missing in the image to cause this sort of error? Thanks, Dean "Ionut Constantinescu" <ad...@radu-negru.ro> wrote in message news:u8rgjxBuIHA.1768@...

... Now nvsvc32.exe is definitely in \windows\system32\, so it must be some other file. However, I ran the install with filemon running, and I can't see anything that would be a showstopper. Any ideas on what may be missing in the image to cause this sort of error? Thanks, Dean "Ionut Constantinescu" <admin@radu-negru.ro> wrote in message news:u8rgjxBuIHA.1768@TK2MSFTNGP03.phx.gbl...

... up a bug in gfortran (PR36186) for which the fix is in the pipeline and the REAL version didn't turn up anything, but the INT version ran into a showstopper that keeps it from compiling: C:\gfortran\james\intrinsics\int>type bug1.f90 module bugmod parameter(ik1 = selected_int_kind(2)) implicit complex (P) contains subroutine bug1(P1) use mykinds1 ...

.... Thanks. (Still sure you don't want to open a http://gcc.gnu.org/bugzilla account?) I was on the cusp of doing that at one point in time but there was something that was a showstopper for me, although I can't remember what it was just off the top of my head. In http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36214 I noticed that if you print out rd, you get 0000000040295400 with the...

... and for initialization and ordinary expressions. I haven't done specification expressions yet because so far they seem to be going the same way as ordinary expressions and gfortran has showstopper issues that have been outstanding for quite a while that might make it more difficult to implement a testing regime for specification expressions. I haven't touched the issue of ...

... all KINDs and for initialization and ordinary expressions. I haven't done specification expressions yet because so far they seem to be going the same way as ordinary expressions and gfortran has showstopper issues that have been outstanding for quite a while that might make it more difficult to implement a testing regime for specification expressions. I haven't touched the issue of array ...

... 8.4 of the language and you run into some code that demands version 6.2 (which has significant incompatibilities or they wouldn't have given it a new major version number) how hard would it be to switch? Could we get a compact easy toolchain? Suppose there were lots of Forthy advantages but the compiled code ran half as fast as a competing compiler written in C. Would that be a showstopper?