Vinzent Hoefler a écrit :
2) If I put the tabstop typographically correct as it should be (that
means: right before the parentheses)[1],
[...]
[1] In normal text( you don't write parentheses like that ), do you?
And what about math functions? Is f (x) more typographically correct
than f(x)?
On Tuesday 22 January 2008 15:18, mm wrote:
Vinzent Hoefler a écrit :
2) If I put the tabstop typographically correct as it should be
(that means: right before the parentheses)[1],
[...]
[1] In normal text( you don't write parentheses like that ), do
you?
And what about math
On Mon, 21 Jan 2008, Damien Gerard wrote:
Is there a standard Coding style for FreePascal (Pascal) available which
programmers should use ?
It is for my boss :)
No, there isn't. I follow Borland coding style, but some others don't.
You cannot force everyone to use the same style. And you
Damien Gerard ha scritto:
Is there a standard Coding style for FreePascal (Pascal) available which
programmers should use ?
It is for my boss :)
these are the FPC documents:
http://wiki.freepascal.org/Coding_style
http://wiki.freepascal.org/DesignGuidelines
but since FreePascal is Object
On 21/01/2008, Michael Van Canneyt [EMAIL PROTECTED] wrote:
No, there isn't. I follow Borland coding style, but some others don't.
You cannot force everyone to use the same style. And you should not.
That's why we need a editor that supports 'elastic tab stops'. ;-)
It's a brilliant idea, but
On 21/01/2008, Michael Van Canneyt [EMAIL PROTECTED] wrote:
No, there isn't. I follow Borland coding style, but some others don't.
You cannot force everyone to use the same style. And you should not.
That's why we need a editor that supports 'elastic tab stops'. ;-)
It's a brilliant
On Monday 21 January 2008 11:59, Marco van de Voort wrote:
I personally would spend my time improving source beautifiers like
our own ptop (and you could make them to automatically find these
tabstops).
Waste of time. Automated tools have never worked so far.
Sure, they can turn totally
On 21/01/2008, Marco van de Voort [EMAIL PROTECTED] wrote:
Such schemes have been tried before, but usually fail since that makes
source only (practically) editable with one editor, which most users loath.
I don't see what's so different about this one.
Also think about e.g. the trouble with
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
As an example where most tools just put out nonsense, consider this:
|type
| CPU_Ins = (Add, Sub, Mul, Div,
| Jnz, Jz, Jnc, Jc,
| Call, Ret,
| Push, Pop,
| ...);
This is so
On Monday 21 January 2008 12:40, Graeme Geldenhuys wrote:
alignment as pretty as can be. But once you save, it inserts the
correct amount of spaces to keep that same alignment on file or
(preferred) inserts the minimum spaces for standard indentation
(Object Pascal uses two spaces for
On Monday 21 January 2008 13:01, Graeme Geldenhuys wrote:
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
As an example where most tools just put out nonsense, consider this:
|type
| CPU_Ins = (Add, Sub, Mul, Div,
| Jnz, Jz, Jnc, Jc,
| Call, Ret,
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
But how would it solve
|type
| FooBar = (Foo,
| Bar);
Look at the flash demo on the website for an example of this!
Lets say gEdit (linux editor) has support for ET.
You would type
type
tabFooBar = (tabFoo,
tabBar );
On Monday 21 January 2008 13:27, Graeme Geldenhuys wrote:
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
But how would it solve
|type
| FooBar = (Foo,
| Bar);
Look at the flash demo on the website for an example of this!
Lets say gEdit (linux editor) has
On Monday 21 January 2008 11:59, Marco van de Voort wrote:
I personally would spend my time improving source beautifiers like
our own ptop (and you could make them to automatically find these
tabstops).
Waste of time. Automated tools have never worked so far.
Depends on you
On Monday 21 January 2008 13:54, Marco van de Voort wrote:
On Monday 21 January 2008 11:59, Marco van de Voort wrote:
Nor does an editor. It can only help. I also think being to focussed
on coding standards (to the point of enforcing) is counterproductive.
As an example where most tools
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
Yes, that's what I figured. But that's wrong. Only legasthenic
retards[1] put spaces at the inside of parentheses.
Padding can be adjusted in the editor supports ET customization so you
wouldn't see the space.
To be more clear on the
On Monday 21 January 2008 13:54, Marco van de Voort wrote:
| Push, Pop,
| ...);
Now, as you can see, the instructions are laid out tabular (a lot
of tools [yes, including elastic tabstops] I've seen so far are
unable to handle even that simple case).
On Monday 21 January 2008 14:23, Graeme Geldenhuys wrote:
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
Yes, that's what I figured. But that's wrong. Only legasthenic
retards[1] put spaces at the inside of parentheses.
Padding can be adjusted in the editor supports ET
On Monday 21 January 2008 14:31, Marco van de Voort wrote:
On Monday 21 January 2008 13:54, Marco van de Voort wrote:
| Push, Pop,
| ...);
Now, as you can see, the instructions are laid out tabular (a
lot of tools [yes, including elastic tabstops]
Graeme Geldenhuys schrieb:
On 21/01/2008, Michael Van Canneyt [EMAIL PROTECTED] wrote:
No, there isn't. I follow Borland coding style, but some others don't.
You cannot force everyone to use the same style. And you should not.
That's why we need a editor that supports 'elastic tab
On Monday 21 January 2008 14:31, Marco van de Voort wrote:
Oh, come on. What if you encounter an enum that does *not* require
such tabbing inside the same source file.
Well, require or not is relative to begin with.
Let me rephrase it: A tool would have destroyed information if it
On Monday 21 January 2008 15:59, Marco van de Voort wrote:
On Monday 21 January 2008 14:31, Marco van de Voort wrote:
Oh, come on. What if you encounter an enum that does *not*
require such tabbing inside the same source file.
Well, require or not is relative to begin with.
Let
On 21/01/2008, Vinzent Hoefler [EMAIL PROTECTED] wrote:
The only difference seems to me, that without tabs the source code still
looks the same, no matter if I look at it in vi, gedit, kate,
or notepad. Once you start using tabs this isn't guaranteed
anymore...
I hope this will be my last
Graeme Geldenhuys wrote:
I hope this will be my last reply. Please take a look at the flash
video on the ET website.
I don't have flash, so I am bound to check out the Java example.
There he uses two editors (gvim and gedit).
With appropriate plugins/scripts, I suppose.
And for the
On 21/01/2008, Vinzent Höfler [EMAIL PROTECTED] wrote:
I'm breaking my own promise and replying again... :)
I hope this will be my last reply. Please take a look at the flash
video on the ET website.
I don't have flash, so I am bound to check out the Java example.
Ask a friend, it's
Graeme Geldenhuys schrieb:
On 21/01/2008, Vinzent Höfler [EMAIL PROTECTED] wrote:
I'm breaking my own promise and replying again... :)
I hope this will be my last reply. Please take a look at the flash
video on the ET website.
I don't have flash, so I am bound to check out the Java
Florian Klaempfl wrote:
Imo that plugin discussion is pretty useless. I'am coding in at least
four different editors pascal (fp ide, joe, lazarus, ultraedit) and I
fear there is no plugin for all editors I use :)
Same here, although the editors' names are a bit different. ;)
Vinzent.
Graeme Geldenhuys wrote:
On 21/01/2008, Vinzent Höfler [EMAIL PROTECTED] wrote:
Yes, that's what I figured. What I don't get is how the editor extracts
the information _back_ from the file after the tabstop information has
been deleted (that's what it does once it gets replaced with spaces).
Is there a standard Coding style for FreePascal (Pascal) available
which programmers should use ?
It is for my boss :)
--
Damien Gerard
[EMAIL PROTECTED]
Le temps n'a pas d'importance. Seul le code est important
-- (f00ty)
___
fpc-pascal
29 matches
Mail list logo
