Problems with "compiler" library

View: New views
1 Messages — Rating Filter:   Alert me  

Problems with "compiler" library

by Adam Chlipala-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I've been using the SML/NJ "compiler" library for a few years now as a
sort of "libsml" to parse and elaborate SML source files and inspect the
resulting environments.  With SML/NJ 110.60, the following code worked
to convert an SML type to a string:

  fun tyToString (STATE {env, ...}) ty =
    PrettyPrint.pp_to_string 65535 (PPType.ppType env) ty

when this source file was compiled in a group that includes:

  $smlnj/compiler/current.cm

Trying to compile the code with SML/NJ 110.65 today, I've found that (I
think) I need to change the first module mentioned on the second line to
"PrettyPrintNew".  However, "current.cm" doesn't seem to export this module.

Can anyone suggest the right code to use to pretty-print a type to a
string in 110.65?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Smlnj-list mailing list
Smlnj-list@...
https://lists.sourceforge.net/lists/listinfo/smlnj-list