visi-lang / visi Goto Github PK

The existing code, especially the Haskell code, needs documentation. Should we use Literate Haskell or just add Haddock style documentation?

Currently the Visi code is exclusively tied to the iPad app. The core Visi language should be separate such that it can be used by multiple sub-projects.

Add syntax to Visi to support built-in documentation a la JavaDocs. Basically, a nice place for docs to sit

Visi models should be, by default, literate. The code should be surroundable by text... the text should be the

Hi,

I couldn't find any build instructions in the README. Are there any docs for building that I've missed?

I'm using cabal version 0.10.2 and ghc 7.0.4 and I got

Linking dist/build/visi/visi ...
ld: warning: could not create compact unwind for .LFB3: non-standard register 5 being saved in prolog
Undefined symbols for architecture i386:
  "_main", referenced from:
      start in crt1.10.6.o
     (maybe you meant: _Main_main2_closure, _Main_main7_info , _Main_main10_info , _Main_main11_srt , _ZCMain_main_info , _Main_main11_closure , _Main_main1_closure , _Main_main8_info , _Main_main11_info , _Main_main_srt , _Main_main9_closure , _Main_main10_closure , _ZCMain_main_srt , _Main_main1_info , _Main_main9_info , _Main_main8_closure , _Main_main7_closure , _Main_main_closure , _Main_main6_closure , _Main_main4_info , _Main_main1_srt , _Main_main5_closure , _Main_main4_srt , _ZCMain_main_closure , _Main_main4_closure , _Main_main7_srt , _Main_main9_srt , _Main_main_info , _Main_main6_info , _Main_main3_closure )
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
cabal: Error: some packages failed to install:
Visi-0.1 failed during the building phase. The exception was:
ExitFailure 1

I understand from the dependency on ghc-iphone that my version of ghc might be too new, but it would be good to have a comprehensive "This is how you get set up" document.

Cheers - looks like a very interesting project!
Ben

I was excited to learn more about Visi until I read

Visi will be self-hosted with a built-in IDE like Smalltalk.

This is exactly why I don't use Squeak or Pharo. I don't want to use your editor, I want to be able to use any editor. And I want to ./hello.visi | anotherprogram, something you can't do when a language is bundled in a horrible non-POSIX, non-CLI VM environment. The few benefits of a Squeak style VM pale in comparison to the loss in flexibility: What if I want to interface Visi with a Perl script? What if I want to run a Visi daemon on bootup?

Please consider using a normal command line environment, providing the IDE as an optional feature.

While I was using visi, I noticed that there was an issue with order operations
in visi

(0.3+0.3+0.3)/3*0.08=3.75

Because of order of operations, the correct answer should be 0.024.
Really the only way 3.75 should show up is

(0.3+0.3+0.3)/(3*0.08)= 3.75

Visi should allow built-in tests for each function and each struct. There needs to be convenient syntax for describing tests. The syntax should dove-tail with the docs syntax. The testing should be as declarative as possible (like Haskell Check).

Over the longer term, there should be reporting and regression analysis tools, but on day 1, we need to have a syntax so that developers write tests by default.

There are no tests in the system. Each module should have unit tests and "check" style tests.

The OS X App (not the library) currently does not compile in XCode.

Currently, the type infererencer will not infer type parameters (if/then/else uses type parameters)

The type checker will not fail if the same "source" is used in a String and a Number operation

This is a ticket... cool