Also "ELSE IF" may spawn a lot of needless END whereas ELIF doesn't need them.
PS:
Sure, in IA32/64 Assembler both ELSE IF and ELIF break into same ASM code like :
cmd
j
[..]
cmd
j
that's ELSE IF and ELIF equals because ASM intructions will excute
sequently (for NOT j = ELSE) even for the E
cmd => cmp
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations
On Tuesday 19 November 2013 09:30:22 Ivanko B wrote:
> Also "ELSE IF" may spawn a lot of needless END whereas ELIF doesn't need
> them.
>
They are not needless, they show the nesting.
Martin
--
Shape the Mobile Experience
On 11/18/2013 10:51 PM, Sieghard wrote:
> Hallo Michael,
>
> Could you please keep sufficient context so even a casual reader can
> surmise what was meant? Thank you.
Nope.
That is what message threads do.
> So you say a single bit can be signed?
Yep. The highest order bit in a number in the "2's
On 11/18/2013 11:03 PM, Sieghard wrote:
> Even if it is larger than any of the other operands?
Yep. That is how it usually is done. Extend or sign-extend after the
operation if the target is larger, truncate if it is smaller.
> Size extend always at runtime?
Yep (If necessary): Adding leading
On 11/18/2013 05:26 PM, Martin Schreiber wrote:
> On Monday 18 November 2013 17:16:03 Ivanko B wrote:
>> Also CASE doesn't accept enumerated type.
> FPC and MSElang do accept enumerated types.
>
C as well. :-)
-Michael
--
On 11/18/2013 08:42 PM, Sieghard wrote:
> Which defeats the intention of case as a _calculated_ selector statement.
How the "jump" is done is up to the compiler optimization not of the
syntax.
For only a few cases it might use just do multiple compares,
For a sequence of numbers with not too many
On 11/18/2013 09:23 PM, Sieghard wrote:
> Though I doubt that there might be any sufficienty urgent need, can't
> you _always_ use any external program for preprocessing any of your
> source files, even be it manually before you compile it? You could
> even use a program compiled with the compil
On 11/18/2013 10:53 PM, Sieghard wrote:
> Now, how can you pass an object that's meant to be kept unaffected by
> anything happening in the procedure or function? Well, yes, you simply
> can't.
Of course you are right. Maybe inventing "constant objects" might be a
nice extension to Object pasca
A problem is that gcc supposedly will not detect that the characters
between single quotes are a string and should not be handled by the
coprocessor.
I did not yet research if/how this behavior can be (in fact gcc _can_
compile pascal code !)
-Michael
On Tuesday 19 November 2013 13:16:36 Michael Schnell wrote:
> On 11/18/2013 10:53 PM, Sieghard wrote:
>
> IMHO it would make more sense to add syntax to allow for static "class"s
> that are not "constructed" (on the heap) but just exist when a variable
> for them is defined (either in global ram or
they show the nesting.
=
What about we don''t need nesting but instead switch independent
alternatives like CASE does ?
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at t
On Tuesday 19 November 2013 15:31:26 Ivanko B wrote:
> they show the nesting.
> =
> What about we don''t need nesting but instead switch independent
> alternatives like CASE does ?
>
"elseif" can not guarantee that semantic is independent of order (do you mean
that with "switch indepen
"case" can.
But "case: only accepts (compile time) contants in its labels so its
usage is restricted.
can not guarantee that semantic is independent of order
Only in case of crossing ranges. Which can be intended for a
particular task BTW.
---
Hallo Ivanko,
Du schriebst am Tue, 19 Nov 2013 13:30:22 +0500:
> Also "ELSE IF" may spawn a lot of needless END whereas ELIF doesn't need
That's wrong impression. Assuming any such construct requires a complete
block constituted by a "begin"-"end" pair, they have exactly the same block
structure
Hallo Martin,
Du schriebst am Tue, 19 Nov 2013 07:05:56 +0100:
> String case labels sometimes are handy and can be implemented by a hash
> table for example.
Certainly. With today's processor's addressing ranges, you might even be
able to compile the hash result into an exhaustive jump table, wh
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 12:55:50 +0100:
> How the "jump" is done is up to the compiler optimization not of the
> syntax.
Not quite - if you allow such complicated constructs, the compiler has to
be complicated - and thus error prone - as well, because it has to be able
t
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 12:40:11 +0100:
[about constant folding]
I sure hope you'll never get to working on a compiler (and fear you might
have already...)
--
--
(Weitergabe von Adressdaten, Telefonnummern u.รค. ohne Zustimmung
nicht gestattet, ebenso Zusendung von Werbu
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 12:32:40 +0100:
> > Could you please keep sufficient context so even a casual reader can
> > surmise what was meant? Thank you.
> Nope.
Alright. I'll not respond to such garbage then.
> > So you say a single bit can be signed?
> Yep. The highest o
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 12:45:18 +0100:
> > FPC and MSElang do accept enumerated types.
> >
> C as well. :-)
C doesn't really _have_ enumerated _types_. It has a means to define
otherwise unavailable symbolic constants using a syntax looking ephemerally
similar to an enum
Hallo Marcos,
Du schriebst am Tue, 19 Nov 2013 00:25:26 -0200:
> > There's no "new ALIAS compiler parameter" neccessary.
>
> I know there is no new ALIAS parameter... So I'm proposing one.
Read completely - there is no ALIAS parameter _neccessary_.
> Ok.
> So, please, explain how we can use __
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 13:16:36 +0100:
> Of course you are right. Maybe inventing "constant objects" might be a
> nice extension to Object pascal.
They've been just resently removed from Delphi. They were called "object"s,
and you _could_ indeed declare constant objects
Hallo Michael,
Du schriebst am Tue, 19 Nov 2013 13:07:41 +0100:
> Of course (for speed) you should not always use a preprocessor. But the
> language should take care that the use of the standard preprocessor (in
_No_ language can make certain that a preprocessor cannot be used.
_No_ language s
END
ELIF THEN BEGIN
...
END
=
In the new (MSElang) syntax, there'll no BEGIN/END here.
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech inn
hash code collisions
SHA256 too ?
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic
C doesn't really _have_ enumerated _types_
=
? It has the "enum" type directly. Don't mix it with #DEFINEd constants.
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at
In the new (MSElang) syntax, there'll no BEGIN/END here.
=
The THEN too :)
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Sof
So, well have:
---
Hmm, "THEN" here will may be needed for syntax ("IF" & "ELIF" are same
level) consistence:
-
IF THEN
...
ELIF THEN
...
ELIF THEN
...
ELIF THEN
...
ELSE [THEN ?]
...
END;
--
28 matches
Mail list logo
