Arthur Ralfs <art...@mathbrane.ca> writes:
| On 11/15/2010 05:20 PM, Gabriel Dos Reis wrote:
| > Arthur Ralfs<art...@mathbrane.ca> writes:
| >
| >
| > | I had to make a few changes concerning lisp package calls involving
| > | strings. I also have a bug now with newlines. I was dealing with
| > | newlines using NewLine$Lisp where
| > |
| > | (defvar |NewLine| '#\NewLine)
| > |
| > | appears in panserver.lisp but that's not working now. How do you
| > | recommend concat'ing a bunch of strings together with newlines in
| > | spad?
| >
| > Let me look into this particular aspect when I'm back tonight.
|
| Reconsidering the bug was again my errant use of "string". To put a
| newline in a string split command I was trying to use
|
| char string NewLine$Lisp
|
| but
|
| char(STRING(NewLine$Lisp)$Lisp)$Character
|
| seems to work. It's very cumbersome compared to "\n".
Hi Arthur,
1. I just merge trunk into ar-sandbox.
2. I agree that notation "\n" is just nicer than the alternative
above. We should work to hide that notation :-)
I just realized that the Character domain does not have an
export for the newline character. That is odd. I'm preparing
patch for that.
In the meantime, I also noticed that the base OpenAxiom (and all
other AXIOMs I suspect) has a global constant $Newline for the
newline character constant. Given that, you can have at the
capsule level
import _$Newline: Character from Foreign Builtin
and then you can convert it to a string writing
_$Newline::String
| > Also, I'll be attending the symbolic-numeric workshop at MSRI from
| > Wednesday through Friday; anything I should me looking into (on a small
| > windows machine) while I'm on the road?
| >
|
| When I call "parseAndEvalToStringEqNum" how do I catch a syntax error?
There is no general exception handling mechanism in Spad -- yet.
However, I'll try to think about a monadic version as stopgap a bit like
the way we do it for possibly failing numeric operations.
-- Gaby
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
open-axiom-devel mailing list
open-axiom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open-axiom-devel
