On 15/04/2019 17:19, Zoë Peterson wrote:
On 4/14/2019 10:41 AM, Jonas Maebe wrote:
That was because Apple did the same with the Objective-C language:
https://en.wikipedia.org/wiki/Objective-C#Objective-C_2.0 :)
How does $modeswitch objectivec1 differ from objectivec2? That article
mentions t
On 4/14/2019 10:41 AM, Jonas Maebe wrote:
That was because Apple did the same with the Objective-C language:
https://en.wikipedia.org/wiki/Objective-C#Objective-C_2.0 :)
How does $modeswitch objectivec1 differ from objectivec2? That article
mentions that Objective-C 2.0 added 64-bit support,
On 4/14/19 9:08 AM, Anthony Walter wrote:
Someone said:
"You can do a {$i mysettings.inc}"
I give that a +1
FWIW: all of the delphi code that i've worked with trying to port to FPC has had
this... at least one had an include file that IFDEF'd its way through like 4 or
5 other pascal compil
> On Apr 14, 2019, at 1:29 PM, Sven Barth via fpc-pascal
> wrote:
>
>> I like what Jonas did for the ObjC mode switch where he named them with
>> versions. Maybe a {$mode objfpc2} one day.
> My idea was to maybe add a mode ObjFPCExt or ObjFPCAdv which is quite a bit
> less conservative and m
Am 14.04.2019 um 17:03 schrieb Ryan Joseph:
On Apr 13, 2019, at 10:07 PM, Ben Grasset wrote:
E.G, I sincerely doubt that anybody has *ever* thought, "man, I sure am glad that
{$mode ObjFPC} does not allowed advanced records. It would be specifically bad if it
did!" because it just doesn't m
Am 14.04.2019 um 04:07 schrieb Ben Grasset:
I dunno about setting them globally, but generally I do find
modeswitches rather annoying, as the combination of features is pretty
arbitrary, and they mostly just *disallow* things that couldn't break
the code of people who weren't using those featur
On 14/04/2019 17:03, Ryan Joseph wrote:
On Apr 13, 2019, at 10:07 PM, Ben Grasset wrote:
E.G, I sincerely doubt that anybody has *ever* thought, "man, I sure am glad that
{$mode ObjFPC} does not allowed advanced records. It would be specifically bad if it
did!" because it just doesn't matt
> On Apr 13, 2019, at 10:07 PM, Ben Grasset wrote:
>
> E.G, I sincerely doubt that anybody has *ever* thought, "man, I sure am glad
> that {$mode ObjFPC} does not allowed advanced records. It would be
> specifically bad if it did!" because it just doesn't matter if they weren't
> using advan
Someone said:
"You can do a {$i mysettings.inc}"
I give that a +1
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Am 14.04.2019 um 04:07 schrieb Ben Grasset:
> I dunno about setting them globally, but generally I do find modeswitches
> rather annoying, as the combination of
> features is pretty arbitrary, and they mostly just *disallow* things that
> couldn't break the code of people who weren't
> using thos
I dunno about setting them globally, but generally I do find modeswitches
rather annoying, as the combination of features is pretty arbitrary, and
they mostly just *disallow* things that couldn't break the code of people
who weren't using those features to begin with if they were allowed.
E.G, I s
Ryan Joseph schrieb am Fr., 12. Apr. 2019,
16:37:
>
>
> > On Apr 12, 2019, at 10:15 AM, Michael Van Canneyt <
> mich...@freepascal.org> wrote:
> >
> > That would break with the rule that directives do not cross unit
> boundaries.
> > It has far-reaching consequences.
> >
> > Better introduce a co
On Fri, 12 Apr 2019, Joao Schuler wrote:
I would use something like {$include mysettings.inc} .
Exactly.
Michael.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Fri, 12 Apr 2019, Ryan Joseph wrote:
On Apr 12, 2019, at 10:15 AM, Michael Van Canneyt
wrote:
That would break with the rule that directives do not cross unit boundaries.
It has far-reaching consequences.
Better introduce a command-line switch to set mode switches.
But is it maybe
> On Apr 12, 2019, at 10:15 AM, Michael Van Canneyt
> wrote:
>
> That would break with the rule that directives do not cross unit boundaries.
> It has far-reaching consequences.
>
> Better introduce a command-line switch to set mode switches.
But is it maybe time we reconsider this or add an
I would use something like {$include mysettings.inc} .
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Fri, 12 Apr 2019, Ryan Joseph wrote:
Can I propose we add a new $modeswitch-all (or some equivalent) that globally
sets modeswitch in all subsequent units? I’m thinking about how messy this list
is getting after these new mode switches are added and that the problem is only
going to grow
Can I propose we add a new $modeswitch-all (or some equivalent) that globally
sets modeswitch in all subsequent units? I’m thinking about how messy this list
is getting after these new mode switches are added and that the problem is only
going to grow. I really like how FPC lets us opt into spec
18 matches
Mail list logo
