Re: [fpc-pascal] FPC code to migrate Outlook PST file to MBOX format?

2019-01-09 Thread brendan
There are several methods available in the market that help your file convert
PST to Office365. You can also use the manual method but its lengthy
process. After a long process, you will be able to convert PST file to
Office 365. If you want to convert all the files at the same time, then you
need to process any smart way. So you need a third party tool that can
change all the files at the same time.
Visit here:- http://www.pstfile.org/mbox/   




--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

[fpc-pascal] when will the size of an enumerated type change?

2019-01-09 Thread Dennis

Type
   TComparisonMode = (cmThisOnly, cmThisAndThat, cmThisOrThat);


TMyClass = class
public
var
   ComparisonMode : TComparisonMode;
end;


I discovered that, the sizeof(ComparisonMode) seem to be different 
depending on whether the type TComparisonMode is defined in the same 
unit file or in another unit file.


Is that possible?

I cannot create a simple test file to test it because the problem only  
appears in my big project.


Does FPC always produce a 4 byte variable for an enumerated types?

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

Re: [fpc-pascal] when will the size of an enumerated type change?

2019-01-09 Thread Michael Van Canneyt



On Wed, 9 Jan 2019, Dennis wrote:


Type
   TComparisonMode = (cmThisOnly, cmThisAndThat, cmThisOrThat);


TMyClass = class
public
var
   ComparisonMode : TComparisonMode;
end;


I discovered that, the sizeof(ComparisonMode) seem to be different 
depending on whether the type TComparisonMode is defined in the same 
unit file or in another unit file.


Is that possible?


If the units are compiled using different settings, yes.



I cannot create a simple test file to test it because the problem only  
appears in my big project.


Does FPC always produce a 4 byte variable for an enumerated types?


No, it depends on the $mode directive and the settings of the packenum 
directive.

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

Re: [fpc-pascal] Constants in generics

2019-01-09 Thread Ryan Joseph


> On Jan 8, 2019, at 3:49 PM, Benito van der Zander  wrote:
> 
> that reminds me of https://bugs.freepascal.org/view.php?id=34232

In this case maybe generics should just not give range errors unless they’re 
specialized? This bug and the problem I have are only for unspecialized 
generics. That would be the easiest and laziest thing to do but it would mean 
this would compile:

type
generic TList = record
list: array[0..0-1] of integer;
end;


Regards,
Ryan Joseph

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

Re: [fpc-pascal] FPC code to migrate Outlook PST file to MBOX format?

2019-01-09 Thread DaWorm
Use the tool that gives you the flat view, then create mail filters in
Thunderbird to move messages to the appropriate folders, and then apply the
filters to the existing messages.  It may take a while to build the
filters, but you'd want to do that anyway so that new messages go to the
right place.

Jeff.

On Wed, May 23, 2018 at 8:19 AM Bo Berglund  wrote:

> Hi,
> I need to switch away from using Outlook 2003 to something sensible
> like Thunderbird. But when I do I need to keep my mail archive, which
> is stored in multiple very big PST files, each organized in a
> folder-subfolder tree. It covers the time from about 1998 to now..
>
> I have tried to find some working converter software available on
> line, but I have failed. Tried a few but they seem to lack the ability
> to handle the internal folders of a PST file.
> One in particular show the full structure of the PST file I select for
> conversion so it looks like it would work. But in the end there is
> only a flat view of email in Thunderbird when I use the created MBOX
> file.
>
> So now I wonder if there is some FPC code around that I can tailor to
> my needs? It seems a pity that the PST -> MBOX conversion should be
> such a problem
>
> The files are real big so I think I will need the 64 bit capability of
> fpc, which I have installed on my laptop.
>
>
> --
> Bo Berglund
> Developer in Sweden
>
> ___
> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] FPC code to migrate Outlook PST file to MBOX format?

2019-01-09 Thread Tomas Hajny
On Wed, January 9, 2019 17:08, DaWorm wrote:
> Use the tool that gives you the flat view, then create mail filters in
> Thunderbird to move messages to the appropriate folders, and then apply
> the filters to the existing messages.  It may take a while to build the
> filters, but you'd want to do that anyway so that new messages go to the
> right place.

This becomes off-topic now (potential replies / follow-ups to fpc-other,
please), but your suggestion implies that sorting into folders is always
automated. That may apply to private e-mails, but most likely not to
company / corporate area, so the recommendation may not apply in general
at least.

Tomas


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

Re: [fpc-pascal] Constants in generics

2019-01-09 Thread Sven Barth via fpc-pascal
Am Mi., 9. Jan. 2019, 17:03 hat Ryan Joseph 
geschrieben:

>
>
> > On Jan 8, 2019, at 3:49 PM, Benito van der Zander 
> wrote:
> >
> > that reminds me of https://bugs.freepascal.org/view.php?id=34232
>
> In this case maybe generics should just not give range errors unless
> they’re specialized? This bug and the problem I have are only for
> unspecialized generics. That would be the easiest and laziest thing to do
> but it would mean this would compile:
>
> type
> generic TList = record
> list: array[0..0-1] of integer;
> end;
>

Which is why I said that this is not the way to go. You need to disable
range checks only for those symbols that must not use it. Maybe add a
"undefined" flag to tconstsym which is set in your
tconstsym.create_undefined and not changed when the const type is changed.

Regards,
Sven

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