Op 2010-11-08 18:55, Hans-Peter Diettrich het geskryf:
>
> The different output problem exists in either case, when every
> application can use a different widget or widgetset, or read config
> files from many different locations.
I was actually referring to software I create. Whatever desktop
When I try to call automated method with string constants, I had the
compile-time error: 'Error: Type is not automatable: "WideString"'.
What I do wrong? Or may be It's a bug?
--- begin verror.pp
{$mode objfpc}
program VError;
var
v : variant;
s : ansistring;
begin
v.
:)
On windows I create a remote thread to be able to pause execution to
enable breakpoints and such while the program is running.
See initialisation part of the gdbmi debugger. There I use a few options
to pause execution. On the NT platform the remote thread solution is the
most reliable.
M
Ok, anyone with an idea..
Attached is a simple program (appologies for the many commented lines,
but all logs refer to the lines as in this source, and I didn't want to
recreate the log yet another time)
Tested with various versions of gdb dwarf debug info (and IIRc (it's
been a lot of trying)
On Mon, 2010-11-08 at 12:53 +0100, Felipe Monteiro de Carvalho wrote:
> On Mon, Nov 8, 2010 at 11:26 AM, Joost van der Sluis wrote:
> LaTeX Warning: Reference `rtl:oldlinux:symlink' on page 948 undefined on input
> line 65407.
>
> (./olinuxex/ex62.pp [948])
>
> ! LaTeX Error: Too deeply nested.
On 08/11/2010 15:27, Paul Ishenin wrote:
08.11.2010 21:54, Jonas Maebe wrote:
Stabs (-gs, the default on most non-64 bit platforms and on Win64) is
legacy and will generally not be updated except for small fixes. Some
things that -gw2 supports and -gs doesn't are declarations of
absolute varia
On 08 Nov 2010, at 19:40, Joost van der Sluis wrote:
> Also, if you use -gw3, all identifiers are not converted to uppercase,
> as -gw2 and -gs do.
You can disable that for stabs with -gp as well.
Jonas
___
fpc-devel maillist - fpc-devel@lists.free
On Mon, 2010-11-08 at 15:54 +0100, Jonas Maebe wrote:
>
> > Is there a list of the advantages, disadvantages of each format.
> (I
> > understand dwarf 3, and 4 are unstable, but what extra features to
> > they add (as in actually implemented features in fpc)
>
> -gw4 does not do anything more
On Mon, 2010-11-08 at 14:07 +0100, Felipe Monteiro de Carvalho wrote:
> On Mon, Nov 8, 2010 at 1:54 PM, Joost van der Sluis wrote:
> > I could send them to you, but you don't need them for the .rpm building.
>
> Ok, so I have generated the rpm with:
>
> make rpm NODOCS=1
That was strictly not n
Graeme Geldenhuys schrieb:
Op 2010-11-08 11:48, Michael Van Canneyt het geskryf:
It gets only really interesting when you start comparing how browsers react
on this DTD reference. In theory, they should react the same. Practice shows
different...
And that's why I stay away from web apps and we
On 08/11/2010 15:27, Paul Ishenin wrote:
08.11.2010 21:54, Jonas Maebe wrote:
Stabs (-gs, the default on most non-64 bit platforms and on Win64) is
legacy and will generally not be updated except for small fixes. Some
things that -gw2 supports and -gs doesn't are declarations of
absolute varia
08.11.2010 21:54, Jonas Maebe wrote:
Stabs (-gs, the default on most non-64 bit platforms and on Win64) is
legacy and will generally not be updated except for small fixes. Some
things that -gw2 supports and -gs doesn't are declarations of absolute
variables, and of properties that map directly
Op 2010-11-08 16:34, Martin het geskryf:
>
> In case it is in the ppu, are later dwarf downward compatible? eg,
> compiling units with -gw3 or -gw4 => will it allow to create an exe with
> -gw1 ?
I can't answer all your other questions, but as per the DWARF spec, 4 is
backward compatible with
On 08 Nov 2010, at 15:34, Martin wrote:
A few questions about the different debug formats (stabs, dwarf
1,2,3(,4))
I don't know at which stage debug info is added: when creating .ppu/
o or when creating .exe
That is to say, when a unit is compiled into a ppu, do you already
need to decid
A few questions about the different debug formats (stabs, dwarf 1,2,3(,4))
I don't know at which stage debug info is added: when creating .ppu/o
or when creating .exe
That is to say, when a unit is compiled into a ppu, do you already need
to decide on which format to use, or can you use one pp
Hello,
On Mon, Nov 8, 2010 at 1:54 PM, Joost van der Sluis wrote:
> I could send them to you, but you don't need them for the .rpm building.
Ok, so I have generated the rpm with:
make rpm NODOCS=1
=D \o/
where should I upload the rpms now? Should I upload both src.rpm and
i386? Should they be
On Mon, 2010-11-08 at 13:35 +0100, Felipe Monteiro de Carvalho wrote:
> On Mon, Nov 8, 2010 at 1:27 PM, Joost van der Sluis wrote:
> > That wasn't the only thing. You created some directory yourself. And
> > stated that the directions were incorrect.
>
> I didn't say they were wrong. I didn't und
Hello FPC,
Monday, November 8, 2010, 10:57:00 AM, you wrote:
>>I don't know HTML well enough to know what all the stuff in DTD files mean
>>or do, but I gather having it listed in the generated HTML is important?
AC> Well, DTD is one W3C recommendation, specifies the rules for correct
AC> renderi
On Mon, 8 Nov 2010, Felipe Monteiro de Carvalho wrote:
LaTeX Warning: Reference `rtl:oldlinux:symlink' on page 948 undefined on input
line 65407.
(./olinuxex/ex62.pp [948])
! LaTeX Error: Too deeply nested.
This probably means that you must increase latex's memory.
If so, that must be done
On Mon, Nov 8, 2010 at 1:27 PM, Joost van der Sluis wrote:
> That wasn't the only thing. You created some directory yourself. And
> stated that the directions were incorrect.
I didn't say they were wrong. I didn't understand the instructions and
asked for clarification. As already mentioned that
On Mon, 2010-11-08 at 12:53 +0100, Felipe Monteiro de Carvalho wrote:
> On Mon, Nov 8, 2010 at 11:26 AM, Joost van der Sluis wrote:
> >> mkdir fpc242/fpcsrc
> >
> > ?!?HUH?!?! No, just follow the instructions. It will make a directory
> > fpcbuild/fpcsrc
>
> ??? Why such a big deal? The directory
On Mon, Nov 8, 2010 at 11:26 AM, Joost van der Sluis wrote:
>> mkdir fpc242/fpcsrc
>
> ?!?HUH?!?! No, just follow the instructions. It will make a directory
> fpcbuild/fpcsrc
??? Why such a big deal? The directory name should be irrelevant.
Anyway, I changed to fpcbuild now.
> No, just 'install
On Fri, 2010-11-05 at 07:18 +0100, Felipe Monteiro de Carvalho wrote:
> Some issues with the instructions. So the commands should be:
?
> svn export http://svn.freepascal.org/svn/fpcbuild/tags/release_2_4_2 fpc242
No? It should be (as in the document):
svn export http://svn.freepascal.org/svn/
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 11:48, Michael Van Canneyt het geskryf:
It gets only really interesting when you start comparing how browsers react
on this DTD reference. In theory, they should react the same. Practice shows
different...
And that's why I stay awa
Graeme wrote:
>I don't know HTML well enough to know what all the stuff in DTD files mean
>or do, but I gather having it listed in the generated HTML is important?
Well, DTD is one W3C recommendation, specifies the rules for correct
rendering
for all browsers. Standards are important, so I think
Op 2010-11-08 11:48, Michael Van Canneyt het geskryf:
>
> It gets only really interesting when you start comparing how browsers react
> on this DTD reference. In theory, they should react the same. Practice shows
> different...
And that's why I stay away from web apps and web development. I like
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 11:31, Amat Coder het geskryf:
You can do that:
Edit html and delete "http://www.w3.org/TR/html4/loose.dtd"; from first line
http://www.w3.org/TR/html4/loose.dtd";>
and even if you don't use any css you can see that no double spaci
Op 2010-11-08 11:31, Amat Coder het geskryf:
>
> You can do that:
> Edit html and delete "http://www.w3.org/TR/html4/loose.dtd"; from first line
>
> "http://www.w3.org/TR/html4/loose.dtd";>
>
> and even if you don't use any css you can see that no double spacing.
>
> This is because 'dtd' for
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 11:03, Michael Van Canneyt het geskryf:
Below is a diff of the lazarus and fpc HTML pages.
With the exception of some header and an extra unit, the
geneated HTML code is the same. The footer is added by sourceforge.
This gave me an
Op 2010-11-08 11:03, Michael Van Canneyt het geskryf:
>
> Below is a diff of the lazarus and fpc HTML pages.
> With the exception of some header and an extra unit, the
> geneated HTML code is the same. The footer is added by sourceforge.
This gave me an idea and I found the difference, and what
Graeme wrote:
>...Because what if you remove
>fpdoc.ss completely, then you still see the double spacing, yet in older
>fpdoc versions there was no double spacing...
You can do that:
Edit html and delete "http://www.w3.org/TR/html4/loose.dtd"; from first line
http://www.w3.org/TR/html4/loose.dtd
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 11:03, Michael Van Canneyt het geskryf:
It is easy to "force" a fix via a CSS file, but clearly there is a HTML
generation problem/difference since June 2009. Even the plain HTML output
(without a css file) is different between now an
Op 2010-11-08 11:03, Michael Van Canneyt het geskryf:
>> It is easy to "force" a fix via a CSS file, but clearly there is a HTML
>> generation problem/difference since June 2009. Even the plain HTML output
>> (without a css file) is different between now and a year ago.
>
> How so ?
With CSS you
Op 2010-11-08 10:49, Michael Van Canneyt het geskryf:
>
> If you look at the first website, the docs are generated march 6, 2010, not
> in 2009.
My reference to June 2009, is the last time I generate tiOPF docs on my server.
The problem came to my attention when I recently wanted to update the t
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 10:43, Amat Coder het geskryf:
td p {
margin: 0;
}
The official FPC docs fpdoc.css doesn't have that in the css file, yet it
outputs correctly.
http://www.freepascal.org/docs-html/rtl/fpdoc.css
That's because there are some o
Op 2010-11-08 10:43, Amat Coder het geskryf:
>
> td p {
> margin: 0;
> }
The official FPC docs fpdoc.css doesn't have that in the css file, yet it
outputs correctly.
http://www.freepascal.org/docs-html/rtl/fpdoc.css
It is easy to "force" a fix via a CSS file, but clearly there is a HTML
ge
On Mon, 8 Nov 2010, Amat Coder wrote:
-- Forwarded message --
From: Amat Coder
Date: 2010/11/8
Subject: [fpc-devel] bug in fpdoc HTML output - double spacing
To: fpc-devel@lists.freepascal.org
Hi.
Please, check css files again.
fpdoc.css from CCR-Lazarus site is:
http://laz
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 10:11, Michael Van Canneyt het geskryf:
The officially generated docs on the website do not have the
problem. They are generated with the latest fpdoc and fpdoc.css.
I tested it with 2 browsers.
As done before I reported the bug, I
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
Op 2010-11-08 10:11, Michael Van Canneyt het geskryf:
Marco didn't close the bug. I did.
Apologies to Marco then.
If you can show that it consistently behaves a certain way,
then we can track and solve the problem, I have no problem
with that
Op 2010-11-08 10:11, Michael Van Canneyt het geskryf:
>
> The officially generated docs on the website do not have the
> problem. They are generated with the latest fpdoc and fpdoc.css.
> I tested it with 2 browsers.
As done before I reported the bug, I did it now (again). I copied the
fpdoc.css
-- Forwarded message --
From: Amat Coder
Date: 2010/11/8
Subject: [fpc-devel] bug in fpdoc HTML output - double spacing
To: fpc-devel@lists.freepascal.org
Hi.
Please, check css files again.
fpdoc.css from CCR-Lazarus site is:
http://lazarus-ccr.sourceforge.net/docs/lcl/fpdoc.css
Op 2010-11-08 10:11, Michael Van Canneyt het geskryf:
>
> Marco didn't close the bug. I did.
Apologies to Marco then.
> If you can show that it consistently behaves a certain way,
> then we can track and solve the problem, I have no problem
> with that. But until now you're the only one that
On Mon, 8 Nov 2010, Graeme Geldenhuys wrote:
@Marco,
If you don't know what is causing the bug or don't know how to fix it,
simply say so and move on. But keep arguing that there is no bug, and
simply marking the bug report as resolved is not the answer! I have clearly
shown to you the differe
43 matches
Mail list logo
