On Mon, September 7, 2009 13:39, David W Noon wrote:
> On Mon, 7 Sep 2009 12:12:42 +0200 (CEST), Michael Van Canneyt wrote
> about Re: [fpc-pascal] The names of the various FPC documentation:
>
>> On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
>>
>> > Such an "o
On Mon, 7 Sep 2009 12:12:42 +0200 (CEST), Michael Van Canneyt wrote
about Re: [fpc-pascal] The names of the various FPC documentation:
> On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
>
> > Such an "old" file-system limitation does not apply in newer OS
> > versions any
My 2 cents are that the worst problem with the docs is this: Very often I do
not know in which one to look for what i want to know or similarly I have to
look in three of them at the same time. In my view rtl and fcl are even more
important than user, ref and prog, and therefore should be includ
On 07 Sep 2009, at 12:30, Frank Peelo wrote:
In Linux, and I guess other unixish OSes like the Mac, it's quite
possible to have spaces or punctuation in file names. That doesn't
mean they're a good idea.
Since they're ubiquitous already anyway on Mac OS X (partly due to its
heritage of c
On 07/09/2009 11:00, Jonas Maebe wrote:
On 07 Sep 2009, at 11:44, Michael Van Canneyt wrote:
On Mon, 7 Sep 2009, Jonas Maebe wrote:
...
Spaces and quotes are vetoed as a general rule :)
That's fine as a general rule, but at least on Mac OS X specifically
it's no problem. I think more
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
Spaces and quotes are vetoed as a general rule :)
Such an "old" file-system limitation does not apply in newer OS versions
anymore. I must say, old habits die hard! :) I often find myself naming
eBooks, TV series
In our previous episode, Jonas Maebe said:
> > Spaces and quotes are vetoed as a general rule :)
>
> That's fine as a general rule, but at least on Mac OS X specifically
> it's no problem. I think more documents and applications (other than
> the command line unix ones) than not have a space i
On 07 Sep 2009, at 11:44, Michael Van Canneyt wrote:
On Mon, 7 Sep 2009, Jonas Maebe wrote:
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
For the Mac OS X releases, I rename them before packing the
installer. The names I use are:
Code Documenter.pdf
Compiler Switches.pdf
Free Compo
Michael Van Canneyt het geskryf:
>
> Spaces and quotes are vetoed as a general rule :)
Such an "old" file-system limitation does not apply in newer OS versions
anymore. I must say, old habits die hard! :) I often find myself naming
eBooks, TV series or music with underscores instead of spaces. Bu
On Mon, 7 Sep 2009, Jonas Maebe wrote:
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
For the Mac OS X releas
Jonas Maebe het geskryf:
> For the Mac OS X releases, I rename them before packing the installer.
> The names I use are:
>
> Code Documenter.pdf
> Compiler Switches.pdf
> Free Component Library.pdf
> Language Reference Guide.pdf
> Programmer's Manual.pdf
> Units Reference Guide.pdf
> User's Manu
Jonas Maebe het geskryf:
>
> For the Mac OS X releases, I rename them before packing the installer.
> The names I use are:
Much better names. :-) I think my main problem is distinguishing
between the Programmers Manual and the Users Manual. See, I am both — so
I never know which PDF to view fo
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
For the Mac OS X releases, I rename them before packing the instal
Michael Van Canneyt het geskryf:
>
> Since you now discovered what each document describes, the problem has
> solved itself :-)
My brain is saturated with other information. By the end of the week I
would have forgotten all this already. :-) To help myself, I locally
renamed the PDF documents to
On Mon, 7 Sep 2009, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Yes I know I can rename them locally, but I also thing it makes sense to
give the documents better "default" names than ref, prog, user.
If there is a more or less consensus about such things, I
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
If there is a more or less consensus about such things, I don't see why
we couldn't rename them.
Glad to hear you are willing to consider this. ;-)
The names actually stem from the TP documentation, which was
> > Yes I know I can rename them locally, but I also thing it makes sense to
> > give the documents better "default" names than ref, prog, user.
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
>
>
I agreed with Graeme.
FPC is very well document
In our previous episode, Graeme Geldenhuys said:
> OK, in the list above "Language Reference" seems obvious, but everywhere
> else (as far as I remember) it is listed as FPC Reference Guide, which
> isn't obvious.
(in the pre-fpdoc past, the reference guide also included the system unit
reference)
Michael Van Canneyt het geskryf:
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
Glad to hear you are willing to consider this. ;-)
> The names actually stem from the TP documentation, which was divided into 3
> books:
> Language Reference
In our previous episode, Michael Van Canneyt said:
> > Yes I know I can rename them locally, but I also thing it makes sense to
> > give the documents better "default" names than ref, prog, user.
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
In our previous episode, Graeme Geldenhuys said:
> Out of those 3 seems to have logical names. rtl, fcl and fpdoc. The
> problem I have is the 'user', 'ref' and 'prog' names. Maybe somebody
> can explain to me how I can remember the various information in each of
> these. For example, if I want to
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Hi,
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
We currently have:
ref.pdf
user.pdf
rtl.pdf
prog.pdf
fcl.pdf
Hi,
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
We currently have:
ref.pdf
user.pdf
rtl.pdf
prog.pdf
fcl.pdf
fpdoc.pdf
Out of those 3 seems to have logi
23 matches
Mail list logo
