ghc VS seed7

Depending on who you ask, a programming language can be different things. If you ask the Haskell community, many will tell you that the language is the Haskell specification, and that what currently is being used is not Haskell itself, but an extension of Haskell that is supported by the GHC compiler. Similar to the C language, a programming language would be a specification.

bss@monster % cat > File.hs pred 1 = 4 succ 4 = 1 succ 1 = 2 bss@monster % ghci -XNoImplicitPrelude File.hs GHCi, version 9.0.2: https://www.haskell.org/ghc/ :? for help Loaded GHCi configuration from /home/bss/.ghc/ghci.conf [1 of 1] Compiling Main ( File.hs, interpreted ) Ok, one module loaded. (0.04 secs,) GHCi> pred 1 4 it :: GHC.Num.Num p => p (0.01 secs, 79,688 bytes) GHCi> succ 1 2 it :: GHC.Num.Num p => p (0.01 secs, 78,088 bytes)

GHCi, version 9.0.2: https://www.haskell.org/ghc/ :? for help Loaded GHCi configuration from /home/bss/.ghc/ghci.conf GHCi> :{ GHCi| pred 1 = 4 GHCi| succ 4 = 1 GHCi| succ 1 = 2 GHCi| :} pred :: (Eq a, Num a, Num p) => a -> p succ :: (Eq a, Num a, Num p) => a -> p (0.04 secs, 0 bytes) GHCi> pred 1 4 it :: Num p => p (0.01 secs, 62,784 bytes) GHCi> succ 4 1 it :: Num p => p (0.01 secs, 61,864 bytes) GHCi> succ 1 2 it :: Num p => p (0.01 secs, 61,928 bytes)

[jumper deriving-trans @master]$ nix develop [jumper deriving-trans @master]$ cabal repl Build profile: -w ghc-9.2.4 -O1 In order, the following will be built (use -v for more details): - deriving-trans-0.8.0.0 (lib) (first run) Preprocessing library for deriving-trans-0.8.0.0.. GHCi, version 9.2.4: https://www.haskell.org/ghc/ :? for help :1:1: warning: [-Wmissing-local-signatures] Polymorphic local binding with no type signature: _compileParsedExpr :: forall {a}. ghc-prim:GHC.Types.IO a -> ghc-prim:GHC.Types.IO a macro 'doc' overwrites builtin command. Use ':def!' to overwrite. Loaded GHCi configuration from /home/jumper/.ghc/ghci.conf : warning: [-Wunused-packages] The following packages were specified via -package or -package-id flags, but were not needed for compilation: - unliftio-core-0.2.0.1-4aEaNp8xHRK6Ey6KEoq0BU - transformers-base-0.4.6-BO3yqj8kK7N1FV1bV9s5yP - transformers-0.6.0.4-F8uVRiS1g8K3h8Rsxr0UMd - resourcet-1.2.6-GkviYKmTWlu24k3qS4ih9J - random-1.2.1.1-DsRhotp5Bx34wv1CRGomTB - primitive-0.7.3.0-1lmZ3PZm6JAE7HP2AgnD1I - mtl-2.3.1-A9dQ96c1wA8f1tgidK0Kj - monad-control-identity-0.2.0.0-C96eAiqAq5HPusYxrNzzr - monad-control-1.0.3.1-9k4XD0NyvERHbSFKJZxIuC - logict-0.8.0.0-5sZNS401Hrq2OkYkpVhzEI - exceptions-0.10.7-LidfE6miSbs6Y1NYj1lBV5 - base-4.16.3.0 [1 of 7] Compiling Control.Monad.Accum.OrphanInstances ( src/Control/Monad/Accum/OrphanInstances.hs, interpreted ) [2 of 7] Compiling Control.Monad.Select.OrphanInstances ( src/Control/Monad/Select/OrphanInstances.hs, interpreted ) [3 of 7] Compiling Control.Monad.Trans.Elevator ( src/Control/Monad/Trans/Elevator.hs, interpreted ) [4 of 7] Compiling Control.Monad.Trans.Compose.Transparent ( src/Control/Monad/Trans/Compose/Transparent.hs, interpreted ) [5 of 7] Compiling Control.Monad.Trans.Compose ( src/Control/Monad/Trans/Compose.hs, interpreted ) [6 of 7] Compiling Control.Monad.Trans.Compose.Stack ( src/Control/Monad/Trans/Compose/Stack.hs, interpreted ) [7 of 7] Compiling Control.Monad.Trans.Compose.Infix ( src/Control/Monad/Trans/Compose/Infix.hs, interpreted ) Ok, 7 modules loaded. λ *Control.Monad.Trans.Compose > :set -XPartialTypeSignatures λ *Control.Monad.Trans.Compose > import Control.Monad.Trans.Compose.Infix λ *Control.Monad.Trans.Compose Control.Monad.Trans.Compose.Infix > import Control.Monad.Trans.Compose.Transparent λ *Control.Monad.Trans.Compose Control.Monad.Trans.Compose.Infix Control.Monad.Trans.Compose.Transparent > runTransparentT ./> (`Mtl.T.runReaderT` 'a') ./> (`Mtl.T.runReaderT` True) $ (,) <$> (Mtl.ask :: _ Char) <*> (Mtl.ask :: _ Bool) :4:98: warning: [-Wpartial-type-signatures] • Found type wildcard ‘_’ standing for ‘ComposeT (Mtl.T.ReaderT Bool) (ComposeT (Mtl.T.ReaderT Char) (Elevator NoT)) IO :: * -> *’ • In the type ‘_ Char’ In an expression type signature: _ Char In the second argument of ‘(<$>)’, namely ‘(Mtl.ask :: _ Char)’ :4:98: warning: [-Wmonomorphism-restriction] • The Monomorphism Restriction applies to the binding for ‘’ Consider giving it a type signature • In the second argument of ‘(<$>)’, namely ‘(Mtl.ask :: _ Char)’ In the first argument of ‘(<*>)’, namely ‘(,) <$> (Mtl.ask :: _ Char)’ In the second argument of ‘($)’, namely ‘(,) <$> (Mtl.ask :: _ Char) <*> (Mtl.ask :: _ Bool)’ :4:122: warning: [-Wpartial-type-signatures] • Found type wildcard ‘_’ standing for ‘ComposeT (Mtl.T.ReaderT Bool) (ComposeT (Mtl.T.ReaderT Char) (Elevator NoT)) IO :: * -> *’ • In the type ‘_ Bool’ In an expression type signature: _ Bool In the second argument of ‘(<*>)’, namely ‘(Mtl.ask :: _ Bool)’ :4:122: warning: [-Wmonomorphism-restriction] • The Monomorphism Restriction applies to the binding for ‘’ Consider giving it a type signature • In the second argument of ‘(<*>)’, namely ‘(Mtl.ask :: _ Bool)’ In the second argument of ‘($)’, namely ‘(,) <$> (Mtl.ask :: _ Char) <*> (Mtl.ask :: _ Bool)’ In the first argument of ‘GHC.GHCi.ghciStepIO :: IO a -> IO a’, namely ‘(runTransparentT ./> (`Mtl.T.runReaderT` 'a') ./> (`Mtl.T.runReaderT` True) $ (,) <$> (Mtl.ask :: _ Char) <*> (Mtl.ask :: _ Bool))’ ('a',True)

GHCi, version 8.10.7: https://www.haskell.org/ghc/ :? for help

Haskell (in the form of GHC) uses Alex, which is regular expression-based.

A good starting point for the JS backend is the module-level documentation in GHC.StgToJS, but it doesn't look like there's much good documentation yet, no.

GHCi, version 9.4.2: https://www.haskell.org/ghc/ :? for help ghci> :load Evolution.hs [1 of 2] Compiling Main ( Evolution.hs, interpreted ) Ok, one module loaded. ghci> :t fac four fac four :: Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ (Succ Zero)))))))))))))))))))))))

Seed7 at GitHub

Yes, I am regularly working on improvements for Seed7. The changes are checked in at GitHub (see here for the list of commits) and once a month I do a release which is announced at r/seed7.

It all depends on the circumstances behind. In the beginning the core-js maintainer had no family and now he has. When I released Seed7 I already had a family. It was clear that my job had to support my family and my hobby (GitHub link).

I improved the explanation in read_me.txt. Now make test is recommended but considered optional as it can also be done later. With make test you can be sure that most of the language works as expected (graphics, sockets and some other things are not tested). Explaining that su should not be used for some commands would probably just add confusion. :-)

If you don't like the Seed7 Homepage at SF you can go to GitHub, Rosetta Code or r/seed7 instead.

Beside the Seed7 Homepage there other sources of information. Several example programs can be found at Rosetta Code. Announcements and discussions take place at r/seed7. Discussions are also in the Seed7 mailing list and announcements are also here. Seed7 is also at GitHub and in Wikipedia.

I just use Emacs without any syntax highlighting for Seed7. Others contributed syntax highlighting files. For vim there is seed7/doc/seed7.vim and seed7/doc/sd7.vim. There is also seed7/doc/seed7.syn and seed7/doc/seed7.uew.

You can find all the released versions of Seed7 at SF and GitHub. There is also r/seed7 where I do announcements.

I invented the program chkccomp.c to find out all properties of C, its run-time and other C libraries (operating system + third party). When you compile Seed7 this program creates hundreds of little test programs that are compiled linked and executed. With that information chkccomp.c writes several hundred lines of property macros to a file named version.h, Other projects use shell scripts for this purpose (./configure comes into mind), but these scripts usually do not work for Windows.

For Seed7 I implemented my own version of CommandLineToArgvW. This function is used if the original one is not available. As mentioned in the article it turned out as much more complicated than expected.