[fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
Hi, FPC and Lazaurs team

I noticed there is new component (PascalScript) ported to
lazarus/components/ and in the past AggPas also ported,
The idea, why you put many components not used for most users, same ask in
FPC

My example to understand me

I use SQLite, we found a bug and this bug fixed by FPC team, now we must
wait long time to have new release with this simple bug fixed.
But if the SQLite unit in another repository, this Extended repo can
published the releases more faster than FPC releases, If FPC release come
one every year this repo collected and released 4 time in this year.

Same idea for Lazarus, i know Lazarus has Lazarus-ccr, for that i asked why
you extending the Components directory in the official Lazarus repository.

Sorry for my poor English.

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Florian Klämpfl 
Am 02.09.2012 11:46, schrieb Zaher Dirkey:
> Hi, FPC and Lazaurs team
> 
> I noticed there is new component (PascalScript) ported to
> lazarus/components/ and in the past AggPas also ported, 
> The idea, why you put many components not used for most users, same ask
> in FPC
> 
> My example to understand me
> 
> I use SQLite, we found a bug and this bug fixed by FPC team, now we must
> wait long time to have new release with this simple bug fixed.
> But if the SQLite unit in another repository, this Extended repo can
> published the releases more faster than FPC releases, 

If somebody is interested to do so, he can do this. What does prevents
someone technically (!) from releasing SQLit unit update installers from
the currently used repository?

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Re: Identifier not found "result"

2012-09-02 Thread Giuliano Colla 

Il 31/08/2012 13:48, leledumbo ha scritto:

I question your assumption that

"Result" is specifically more important than the other incompatibilities
among different modes (i.e. your statement that it "will help...a lot"). I
do not say that it is wrong to be more helpful in error messages, but
rather that your proposal tries to "fix" a very small fragment of
something much more general and moreover that the proposed message may be
very easily misleading as already demonstrated by Mark. Yet other cases
might not be detected by the compiler at all:

+1. Since Result is not really special, i.e. it can be declared by user, it
would be difficult to detect whether it's user's intention or not.

Treating just Result as a special case might not be worth while.

However a more general feature could perhaps be useful:
as the compiler knows all the keywords of all its modes, if an 
unresolved identifier happens to match a keyword of a different mode, a 
warning, sort of "wrong mode?" could be added. The overhead should be 
negligible, because it would occur only in case of unresolved 
identifier, and after a few of them compilation is stopped in any case.


Giuliano

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Martin 

On 02/09/2012 11:46, Zaher Dirkey wrote:

Hi, FPC and Lazaurs team

I noticed there is new component (PascalScript) ported to 
lazarus/components/ and in the past AggPas also ported,



...
I use SQLite, we found a bug and this bug fixed by FPC team, now we 
must wait long time to have new release with this simple bug fixed.
But if the SQLite unit in another repository, this Extended repo can 
published the releases more faster than FPC releases, If FPC release 
come one every year this repo collected and released 4 time in this year.


The reason Pascalsript went into the main SVN is, that (if all goes 
well) then it will be used by the IDE itself. So the IDE will need it to 
be build.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
On Sun, Sep 2, 2012 at 1:20 PM, Florian Klämpfl wrote:

> If somebody is interested to do so, he can do this. What does prevents
> someone technically (!) from releasing SQLit unit update installers from
> the currently used repository?
>

Partial agree, but
In another repo, you can have separated milestones, bugs must finished
before release the new version, it is like when release Lazarus based on
the same versions of FPC.

Not only Sqlite, there is many packages like it, sqlite here for example.

snapshots not resolve the problem because it have included the core of FPC,
and it is not stable.

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

[fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Reinier Olislagers 
On 2-9-2012 13:22, Zaher Dirkey wrote:
> On Sun, Sep 2, 2012 at 1:20 PM, Florian Klämpfl
>  > wrote:
> 
> If somebody is interested to do so, he can do this. What does prevents
> someone technically (!) from releasing SQLit unit update installers from
> the currently used repository?
> 
> 
> Partial agree, but
> In another repo, you can have separated milestones, bugs must finished
> before release the new version, it is like when release Lazarus based on
> the same versions of FPC.
> 
> Not only Sqlite, there is many packages like it, sqlite here for example.
> 
> snapshots not resolve the problem because it have included the core of
> FPC, and it is not stable.

Why don't you use FPC fixes (e.g. FPC 2.6.1) then, and help backport
stable fixes from trunk to fixes?

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
On Sun, Sep 2, 2012 at 2:18 PM, Martin  wrote:

> The reason Pascalsript went into the main SVN is, that (if all goes well)
> then it will be used by the IDE itself. So the IDE will need it to be build.


That is good news for me :)

I also mentioned AggPas, if it have the same reason i think we need more
searches to understand the code changes, but no problem.

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
On Sun, Sep 2, 2012 at 2:25 PM, Reinier Olislagers <
reinierolislag...@gmail.com> wrote:

>
> Why don't you use FPC fixes (e.g. FPC 2.6.1) then, and help backport
> stable fixes from trunk to fixes?


Is that in the download page?
And is it have the last fixed for this kind of non core packages?

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

[fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Reinier Olislagers 
On 2-9-2012 13:30, Zaher Dirkey wrote:
> 
> On Sun, Sep 2, 2012 at 2:25 PM, Reinier Olislagers
>  > wrote:
> 
> 
> Why don't you use FPC fixes (e.g. FPC 2.6.1) then, and help backport
> stable fixes from trunk to fixes?
> 
> 
> Is that in the download page?
It's a branch in the svn repository. And Lazarus builds based on fixes
2.6 appear on the snapshots page. For Linux/OSX, you'll probably find
those on the snapshots page.
For fpc only: see also
http://www.freepascal.org/develop.var

Anyway, I'd rather use svn - of course, in my case fpcup ;) because I
don't want to download the entire distribution all the time, only the
changes.

> And is it have the last fixed for this kind of non core packages?
It has the last fixes that were considered stable and were backported
for all FPC packages.

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
On Sun, Sep 2, 2012 at 2:55 PM, Reinier Olislagers <
reinierolislag...@gmail.com> wrote:

> It's a branch in the svn repository. And Lazarus builds based on fixes
> 2.6 appear on the snapshots page. For Linux/OSX, you'll probably find
> those on the snapshots page.
> For fpc only: see also
> http://www.freepascal.org/develop.var
>
> Anyway, I'd rather use svn - of course, in my case fpcup ;) because I
> don't want to download the entire distribution all the time, only the
> changes.
>
>
It is for expert user not for normal user.


> > And is it have the last fixed for this kind of non core packages?
> It has the last fixes that were considered stable and were backported
> for all FPC packages.
>

So, i prefer to make fixes snapshots in the main downloads page but with
minor version number like this 2.6.0.1, because: how can i publish my
project and mentioned what snapshot must used to work or compiled?.

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

[fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Reinier Olislagers 
On 2-9-2012 14:10, Zaher Dirkey wrote:
> On Sun, Sep 2, 2012 at 2:55 PM, Reinier Olislagers
>  > wrote:
> 
> It's a branch in the svn repository. And Lazarus builds based on fixes
> 2.6 appear on the snapshots page. For Linux/OSX, you'll probably find
> those on the snapshots page.
> For fpc only: see also
> http://www.freepascal.org/develop.var
> 
> Anyway, I'd rather use svn - of course, in my case fpcup ;) because I
> don't want to download the entire distribution all the time, only the
> changes.
> 
> 
> It is for expert user not for normal user.
Nothing difficult in running fpcup ;)
Regardlessly, have a look at the pages I linked to for the nightly download.

> > And is it have the last fixed for this kind of non core packages?
> It has the last fixes that were considered stable and were backported
> for all FPC packages.
> 
> 
> So, i prefer to make fixes snapshots in the main downloads page but with
> minor version number like this 2.6.0.1, because: how can i publish my
> project and mentioned what snapshot must used to work or compiled?.
If the fixes branch breaks it needs to be... fixed.
Because only fixes, no new functionality, are backported to FPC fixes
after having been tested for a while in FPC trunk, that shouldn't happen
very much.

Apart from that I don't really understand. Are you saying you want to
maintain your own FPC distribution that contains fixes so people can use
it to compile your software?

Sounds like a lot of work.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Access to compiler's internal data structures

2012-09-02 Thread Kenneth Cochran 
My goal is to make it an IDE expert so the CodeTools parser sounds ideal.
Just didn't want to reinvent the wheel. I also wanted to avoid the problem
Delphi has been plagued with for years, that is, CodeInsight flagging code
with syntax errors that the compiler readily accepts because they use
different parsers.
On Sep 1, 2012 3:54 AM, "Bernd"  wrote:

> 2012/8/31 Kenneth Cochran :
>
> > I'm finding myself in need of a parser for object pascal. I'm wondering
> if
> > fpc exposes any of the output (syntax trees, graphs, etc) from the parser
> > that could be consumed by an external tool?
>
> Depending on what exactly you need and how difficult it is to get a
> syntax tree from the compiler itself there exist at least two more
> parsers that *might* be useful for you: one of them is in the
> CodeTools package in Lazarus and is used for autocomplete,
> refactoring, etc and another totally separate parser is in the Jedi
> code formating package (also part of Lazarus) that is used for
> re-formatting the code of a single unit.
>
> These parsers were written with different goals in mind and for
> different purposes, so they work slightly different and provide
> different output, for example the jedi parser will only parse one unit
> (and is not very closely connected with the IDE and can probably
> easily be ripped out of it and be used in a separate project) while
> the codetools parsers are able to follow used units, include files,
> respect currently active defines, etc. but are deeply integrated into
> the IDE and probably also depending on many parts of he IDE.
>
> If the project you have in mind would be something that helps coding
> or understanding and analyzing existing code it might probably be very
> nice to have it available as a part of the Lazarus IDE (as an
> installable package) and let it extend the CodeTools parsers.
> ___
> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal
>
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Access to compiler's internal data structures

2012-09-02 Thread Michael Van Canneyt 



On Sun, 2 Sep 2012, Kenneth Cochran wrote:



My goal is to make it an IDE expert so the CodeTools parser sounds ideal. Just 
didn't want to reinvent the wheel. I also wanted
to avoid the problem Delphi has been plagued with for years, that is, 
CodeInsight flagging code with syntax errors that the
compiler readily accepts because they use different parsers.


You'll still be plagued with that, since the codetools are not the same as the 
compiler ?
(although they come close)

Michael.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Re: About Putting everything in one repo

2012-09-02 Thread Zaher Dirkey 
On Sun, Sep 2, 2012 at 3:30 PM, Reinier Olislagers <
reinierolislag...@gmail.com> wrote:

> Apart from that I don't really understand. Are you saying you want to
> maintain your own FPC distribution that contains fixes so people can use
> it to compile your software?
>

No :)

I need more faster release versions, no need to include release a core
files, only packages with minor version number, most product i used it have
this release like PHP, SQLITE, FirebirdSQL.

not using snapshots or SVN.

Best Regards
Zaher Dirkey
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Re: Identifier not found "result"

2012-09-02 Thread Sven Barth 

On 02.09.2012 12:39, Giuliano Colla wrote:

Il 31/08/2012 13:48, leledumbo ha scritto:

I question your assumption that

"Result" is specifically more important than the other incompatibilities
among different modes (i.e. your statement that it "will help...a
lot"). I
do not say that it is wrong to be more helpful in error messages, but
rather that your proposal tries to "fix" a very small fragment of
something much more general and moreover that the proposed message may be
very easily misleading as already demonstrated by Mark. Yet other cases
might not be detected by the compiler at all:

+1. Since Result is not really special, i.e. it can be declared by
user, it
would be difficult to detect whether it's user's intention or not.

Treating just Result as a special case might not be worth while.

However a more general feature could perhaps be useful:
as the compiler knows all the keywords of all its modes, if an
unresolved identifier happens to match a keyword of a different mode, a
warning, sort of "wrong mode?" could be added. The overhead should be
negligible, because it would occur only in case of unresolved
identifier, and after a few of them compilation is stopped in any case.


1. "Result" is never a keyword.

2. There are context sensitive keywords that are not considered as 
global keywords in any mode (e.g. "read" and "write" of properties) and 
thus only the part that parses them (in the example the parser for 
properties) "knows" that it should consider these identifiers as keywords.


Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] About Putting everything in one repo

2012-09-02 Thread Sven Barth 

On 02.09.2012 11:46, Zaher Dirkey wrote:

Hi, FPC and Lazaurs team

I noticed there is new component (PascalScript) ported to
lazarus/components/ and in the past AggPas also ported,
The idea, why you put many components not used for most users, same ask
in FPC

My example to understand me

I use SQLite, we found a bug and this bug fixed by FPC team, now we must
wait long time to have new release with this simple bug fixed.
But if the SQLite unit in another repository, this Extended repo can
published the releases more faster than FPC releases, If FPC release
come one every year this repo collected and released 4 time in this year.


There is the idea to have some/most/all units under packages being 
distributed by a FPC package manager (which already exists more or less: 
fppkg) which can update the installed packages. The switch from fpcmake 
to fpmake is a first step in that direction, but I don't know how high 
the motivation for a package manager is...


Note: In concept it would be similar to package managers for other 
programming languages like Python, Ruby or Lua.


Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal