Re: [fpc-devel] Problems with viewcvs
On 9/28/06, Florian Klaempfl <[EMAIL PROTECTED]> wrote: Fixed. Uau! that must be a record =) -- Felipe Monteiro de Carvalho ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Problems with viewcvs
Felipe Monteiro de Carvalho schrieb: Hello, I tryed accessing the viewcvs page for free pascal: http://www.freepascal.org/cgi-bin/viewcvs.cgi/?root=fpc But it gives this error: An Exception Has Occurred Python Traceback Traceback (most recent call last): File "/srv/viewcvs/lib/viewcvs.py", line 3355, in main request.run_viewcvs() File "/srv/viewcvs/lib/viewcvs.py", line 257, in run_viewcvs import vclib.svn File "/srv/viewcvs/lib/vclib/svn/__init__.py", line 27, in ? from svn import fs, repos, core, delta File "/usr/lib/python2.4/site-packages/svn/fs.py", line 28, in ? import libsvn.fs File "/usr/lib/python2.4/site-packages/libsvn/fs.py", line 5, in ? import _fs ImportError: libsvn_swig_py-1.so.0: cannot open shared object file: No such file or directory thanks, Fixed. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] Problems with viewcvs
Hello, I tryed accessing the viewcvs page for free pascal: http://www.freepascal.org/cgi-bin/viewcvs.cgi/?root=fpc But it gives this error: An Exception Has Occurred Python Traceback Traceback (most recent call last): File "/srv/viewcvs/lib/viewcvs.py", line 3355, in main request.run_viewcvs() File "/srv/viewcvs/lib/viewcvs.py", line 257, in run_viewcvs import vclib.svn File "/srv/viewcvs/lib/vclib/svn/__init__.py", line 27, in ? from svn import fs, repos, core, delta File "/usr/lib/python2.4/site-packages/svn/fs.py", line 28, in ? import libsvn.fs File "/usr/lib/python2.4/site-packages/libsvn/fs.py", line 5, in ? import _fs ImportError: libsvn_swig_py-1.so.0: cannot open shared object file: No such file or directory thanks, -- Felipe Monteiro de Carvalho ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Suggestion for change: Overly strict check
Christian Iversen wrote: > rare, however - and you have to be careful anyway, because this restriction > is not consistent: > > var > wait: boolean; > > procedure tfoo.ReadStuff(buffer: tbuffer; wait: boolean); > begin > // In here, wait could refer either to the parameter, or the global var. > end; If the goal is consistency, I'd rather disable this scenario (with an appropriate error message) as well, rather than enable the other scenario. > However, it's not confused with the global var, because standard scoping > rules > apply. Same as with inner functions and such. Also, if you have a unit foo, It's not about confusion to the compiler, it's about confusion to the reader of the code :-). Micha ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Suggestion for change: Overly strict check
On Wed, 27 Sep 2006, Christian Iversen wrote: > > Hi all. > > I was hoping there could be a discussion of a certain feature in FPC, which > doesn't work very well for us. Ultimately, I would like to see it gone > completely. It's a very small extra-strong syntax check, appearantly > implemented to avoid bad code. However, it's not entirely obvious why this is > supposed to help. > > Please consider this example: > > type > tfoo = class(tbar) > private > public > procedure Frob(); > procedure Wait(delay: integer); > procedure ReadStuff(buffer: tbuffer; wait: boolean); > end; > > When declaring classes or interfaces, it is specifically checked that the > names of methods are NOT the same as _any_ variable name of _any_ other > method in the class. This means that the example above will NOT compile. > > > Now, in Delphi mode this check is not performed, and so the code above will > compile without problems. So, compile using Delphi mode. What's the problem ? The check ensures that the namespace of the class is cleaner than in Delphi. I have had several live examples where FPC has caught a bug in my Delphi code like this. So it stays in as far as I'm concerned, I think it is a very good check. At the best, we could provide a command-line switch or directive to disable or enable this check, but I would not recommend this at all. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] Suggestion for change: Overly strict check
On Wednesday 27 September 2006 20:50, ik wrote: > Let me give you an example of a real bug that allow attackers to gain > root access using X-server, and I hope you will understand why such > checking can be a good thing. It *can*. But as usual the pros and cons should be weighted properly. Although I usually like tremendous amounts of compiler checks, because they save my time, I have to agree with Christian here. This sort of "syntax" check is far too strict. If at all, it should be a warning and *only* if the types could actually be confused. Forcing people to use Hungarian Notation, like it was already suggested, to avoid this check doesn't help neither, there are enough examples for that. (Granted, maybe this is due to the fact, that I always write "self. ..." for an object method/variable, so local names can't get confused in such a way at all.) Vinzent. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
