move parfait to architecture

typed will retired soon
This commit is contained in:
Torsten Ruger 2018-04-11 19:44:01 +03:00
parent 3ac0745c8e
commit 8787a77d14
6 changed files with 10 additions and 17 deletions

View File

@ -2,6 +2,8 @@
%ul.nav
%li
%a{:href => "/rubyx/layers.html"} Layers of RubyX
%li
%a{:href => "/rubyx/parfait.html"} Parfait
%li
%a{:href => "/rubyx/memory.html"} Memory
%li

View File

@ -1,8 +1,6 @@
- title = "RubyX architectural layers"
= render "pages/rubyx/menu"
%h1#main-layers Main Layers
%h1=title "RubyX architectural layers"
%p
To implement an object system to execute object oriented languages takes a large system.
The parts or abstraction layers are detailed below.

View File

@ -1,8 +1,6 @@
- title = "Types, memory layout and management"
= render "pages/rubyx/menu"
%h1#main-layers Memory management
%h1=title "Types, memory layout and management"
%p Memory management must be one of the main horrors of computing. Thats why garbage collected languages like ruby are so great. Even simple malloc implementations tend to be quite complicated. Unnecessary so, if one used object oriented principles of data hiding.
%h3#object-and-values Object and values

View File

@ -1,8 +1,6 @@
- title = "Optimisation ideas"
= render "pages/rubyx/menu"
%h1 Optimisation ideas
%h1=title "Optimisation ideas"
%p I wont manage to implement all of these idea in the beginning, so i just jot them down.
%h3#avoid-dynamic-lookup Avoid dynamic lookup

View File

@ -1,8 +1,7 @@
%hr/
%p
layout: typed
title: Parfait, a minimal runtime
= render "pages/rubyx/menu"
%h1= title "Parfait, a minimal runtime"
%h3#type-and-class Type and Class
%p
Each object has a type that describes the instance variables and basic types of the object.

View File

@ -1,8 +1,6 @@
- title = "Threads are broken"
= render "pages/rubyx/menu"
%h1 "Threads are broken"
%h1= title "Threads are broken"
%p
Having just read about rubys threads, i was moved to collect my thoughts on the topic. How this will influence implementation