On 18/05/2012, at 9:54 AM, john skaller wrote:
>
> On 18/05/2012, at 3:47 AM, Raoul Duke wrote:
>
>> otherwise known as structural typing?
>
> Well we could say
>
> interface Fred {
> getx: 1 -> int;
> };
BTW: .. records can be polymorphic so ..
interface Fred[T] { ...
However Felix objec
On 18/05/2012, at 3:47 AM, Raoul Duke wrote:
> otherwise known as structural typing?
Well we could say
interface Fred {
getx: 1 -> int;
};
interface Joe extends Fred {
gety: 1 -> int;
}
and it looks like Java ... :)
But it's actually just a typedef for a record type :)
And we might have
otherwise known as structural typing?
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will i
Felix has been able to do OO for some time, it just isn't sugared.
Here's an example:
//
// An OO experiment
fun X (var x:int, var y:int) = {
proc setx(a:int) { x = a; }
proc sety(a:int) { x = a; }
fun getx() => x;
fun gety () => y;
fun sum () => x + y;
return (setx=
Im still struggling with the install layout.
This makes sense:
felix/share/felix-version/lib/std/*.flx ... etc etc
Each version has a new standard library, tool sources, etc.
This would also cover C++ sources.
Now, the platform dependent stuff is in two parts:
(a) configuration data: *.fpc fil
