User talk:FTurtle

From Free Pascal wiki

G'day FTurtle,

I see you changed "Mac OS X" to "MacOS" which is a little unfortunate because there is no such thing.

The history of Apple's operating system naming goes like this:

  • Mac OS aka Classic Mac OS until 2006
  • Mac OS X until 2012
  • OS X until 2016
  • macOS since 2017.

So, you have picked the worst possible name for the category, a name which refers to pre 2006 Classic Mac OS!

Could you please pick another category name?

Thanks Trev (talk) 21:55, 12 December 2019 (CET)


Hello Trev,

Be more watchful:

1. Redirection macOS -> Mac OS X made in 2016 by Jwdietrich:

(cur | prev) 23:49, 13 June 2016‎ Jwdietrich (talk | contribs)‎ . . (31 bytes) (+31)‎ . . (creating this new category as an alias for category "Mac OS X" (necessary for some templates))

My fault is I made Category:MacOS when exists Category:macOS

The possible solutions:

1. Change redirection from macOS -> Mac OS X to macOS ->MacOS

2. Delete MacOS and make all needed changes for macOS.

As for all other, see:

P.S. I hope you begin work with wiki from page every time

FTurtle (talk) 23:34, 12 December 2019 (CET)


The best possible outcome is probably (2) Delete MacOS and make all needed changes for macOS as one category to rule them all from 2006. Classic Mac OS is still needed because it predates Intel processors from 2006 and refers to PowerPC processors and so completely different programming considerations apply, although I do not know whether Lazarus really still supports the pre-2006 operating system or whether it could be consigned to the dustbin of history and re-tagged Historical Mac OS.

As for templates, I'm a neophyte and do not touch any that I don't fully understand so as to avoid unintended consequences and work for others to fix.

Next steps? I'm happy to re-tag everything (other than "Mac OS Classic") as macOS and remove "OS X" and "Mac OS X" if you take care of the template.

Recent Changes: Yes, I always keep an eye on them and have my RSS feed keep the last 100.

Trev (talk) 00:10, 13 December 2019 (CET)


OK. I will see some things like linked references and etc for prevent break anything. I hope I will have time at Sunday.

FTurtle (talk) 23:16, 13 December 2019 (CET)


Excellent - I believe I have rationalised the categories on every Mac-related wiki page and template as of today - "macOS" and/or "Mac OS Classic".

Trev (talk) 06:42, 14 December 2019 (CET)


Thanks for your work on the Mac-related templates!

Trev (talk) 02:30, 16 December 2019 (CET)

Hello FTurtle,

what do you want to show with the creation of endless categories? They are unhelpful and superfluous. Please stop your actions. Regards, --Swen 22:29, 24 July 2015 (CEST)

Hello Swen.

May be, long list of new categories looks little strange, but I will explain. I categorized almost all pages in wiki. Earlier many categories contained long lists of articles with same names and different languages. I included pages of different languages to categories with according of their language. So, now in English hierarchy we see only English articles. And the same way German, Russian and etc. Each article should be at least in one category. And any article should be accessible by walking via categories from root category Category:Main/lng of own language hierarchy. So, should exist all categories betwen Main/lng and category in which included article. As I said, now all pages already included in proper categories. But some categories not exist but required. That categories we can see here:

I create only required categories and any category contain at least one page or category. Now left 219 categories. List may be little increase if some categories will make red links. It is a single-time action after which all will systematized. I think that about 200 categories not increase weight to server too much. And that categories will not clog the wiki.

I ask you to allow me complete this work in discribed range.

FTurtle 23:39, 24 July 2015 (CEST)


Why did you remove redirects like Run time library to RTL and nominated them for deletion? Redirects are imho most useful as they prevent useless creation of already existing topics - Arent (talk) 13:31, 14 July 2016 (CEST)

Run time library and RTL are the same thing.

Why not create other redirects like these:

  • Run-time library
  • Runtime library
  • run time library
  • runtime library
  • run-time library

If every user will create redirect for his own convenience for each page then we will have no wiki but heap of garbage.

FTurtle (talk) 18:25, 14 July 2016 (CEST)

Qoute of myself:

If every user will create redirect for his own convenience for each page then we will have no wiki but heap of garbage.

I see you alredy do it:

  • pcp
  • primary config path‎
  • Primary Config Path‎

FTurtle (talk) 18:45, 14 July 2016 (CEST)

We happen to disagree about this. Redirects cost near to nothing and are great for easy access. I was looking for the RTL but searched for Run time library which was a disabled redirect. From the history I got to the place I was looking for. For what its worth, most wikipedias rely on it (this discussion has been held over and over). No need to create all case-different possibilities of every topic beforehand, but things pcp/Primary Config Path‎ both should be search topics. - Arent (talk) 21:30, 14 July 2016 (CEST)
Redirects are sometimes useful. But they should be used only when really necessary. For example, when you move old page, redirect may save working links from outside (for example, from forum). Or, sometimes, for searching by different names of something. Anyway, all links in wiki should only refer to original page, but not on redirections (at least when you create new links). FTurtle (talk) 22:18, 14 July 2016 (CEST)



Я тут первий день! Я буду добавлять документацию на украинском. Если что - можно обращаться? С уважением, --Nickispeaki (talk) 11:45, 19 January 2017 (CET)

Да, конечно. Прошу извинить за задержку с ответом - пропустил сообщение. FTurtle (talk) 17:13, 16 February 2017 (CET)

About "Other Firebird libraries"

Hello FTurtle,

Many thanks for the information. I went back on this page and the french version is now a translated one.

self in static methods

Well, yeah, self is available in static methods:

program staticMethods(input, output, stderr);

	foo = object
			x: longint; static;
			function bar(): longint; static;

function longint;
	bar := self.x;


This compiles and works. Kai Burghardt (talk) 14:46, 26 May 2018 (CEST)

I forgot about objects. In classes static methods always are class methods. So, when I wrote "static method" I meant "static class method". This wording is correct for both: classes and objects. You can check validity ot this wording for objects by changing:


  function bar(): longint; static;


  class function bar(): longint; static;

You will get error:

project1.lpr(13,9) Error: Identifier not found "self"

Also see links:

FTurtle (talk) 18:36, 26 May 2018 (CEST)