Indented multiline literals - Revision history

Kevin Reid: add info on second report

Kevin Reid — Fri, 16 Jan 2009 00:55:10 GMT

add info on second report

New page

The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[quasi-literal]]s which is indifferent to the level of indentation in human-written programs.

==Proposals==

Several made in [http://www.eros-os.org/pipermail/e-lang/2009-January/012968.html]. [If opinions are expressed, expand this section to mention them specifically.]

==Discussion==

* [http://www.eros-os.org/pipermail/e-lang/2008-March/012520.html Initial report] by [[User:Kevin Reid]].
* [http://www.eros-os.org/pipermail/e-lang/2009-January/012968.html Second report] by Kevin Reid (who forgot he had written the first)

[[Category:Unresolved design issues]]

Kevin Reid: link to topic page for quasi-literals rather than into the Walnut

Kevin Reid — Wed, 05 Mar 2008 01:45:53 GMT

link to topic page for quasi-literals rather than into the Walnut

←Older revision		Revision as of 01:45, 5 March 2008
Line 1:		Line 1:
-	The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[~~Walnut/Ordinary_Programming/Quasi-Literals_and_Quasi-Parsers\|~~quasi-~~literals~~]] which is indifferent to the level of indentation in human-written programs.	+	The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[quasi-literal]]s which is indifferent to the level of indentation in human-written programs.

	==Proposals==		==Proposals==

Kevin Reid: remove pretentious and distracting highlighting of 'E'

Kevin Reid — Wed, 05 Mar 2008 01:39:25 GMT

remove pretentious and distracting highlighting of 'E'

←Older revision		Revision as of 01:39, 5 March 2008
Line 1:		Line 1:
-	The ~~'''''~~E~~'''''~~ parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[Walnut/Ordinary_Programming/Quasi-Literals_and_Quasi-Parsers\|quasi-literals]] which is indifferent to the level of indentation in human-written programs.	+	The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[Walnut/Ordinary_Programming/Quasi-Literals_and_Quasi-Parsers\|quasi-literals]] which is indifferent to the level of indentation in human-written programs.

	==Proposals==		==Proposals==

Ansible: link for quasi-literals

Ansible — Tue, 04 Mar 2008 21:01:44 GMT

link for quasi-literals

←Older revision		Revision as of 21:01, 4 March 2008
Line 1:		Line 1:
-	The '''''E''''' parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and quasi-literals which is indifferent to the level of indentation in human-written programs.	+	The '''''E''''' parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and [[Walnut/Ordinary_Programming/Quasi-Literals_and_Quasi-Parsers\|quasi-literals]] which is indifferent to the level of indentation in human-written programs.

	==Proposals==		==Proposals==

Ansible: Fixing the '''''E'''''.

Ansible — Tue, 04 Mar 2008 21:00:03 GMT

Fixing the '''''E'''''.

←Older revision		Revision as of 21:00, 4 March 2008
Line 1:		Line 1:
-	The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and quasi-literals which is indifferent to the level of indentation in human-written programs.	+	The '''''E''''' parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and quasi-literals which is indifferent to the level of indentation in human-written programs.

	==Proposals==		==Proposals==

Kevin Reid: useful for other than consistency

Kevin Reid — Mon, 03 Mar 2008 14:05:58 GMT

useful for other than consistency

←Older revision		Revision as of 14:05, 3 March 2008
Line 1:		Line 1:
-	The E parser and printer fail to be consistent when given a string literal containing a line break.	+	The E parser and printer fail to be consistent when given a string literal containing a line break. It would also be useful to have syntax for multi-line string and quasi-literals which is indifferent to the level of indentation in human-written programs.

	==Proposals==		==Proposals==

Kevin Reid at 14:02, 3 March 2008

Kevin Reid — Mon, 03 Mar 2008 14:02:19 GMT

←Older revision		Revision as of 14:02, 3 March 2008
Line 1:		Line 1:
-	The E parser and printer fail to be consistent when given a string literal containing a line break~~. It would also be useful to have syntax for multi-line string and [[quasi-literal]]s which is indifferent to the level of indentation in human-written programs~~.	+	The E parser and printer fail to be consistent when given a string literal containing a line break.

	==Proposals==		==Proposals==

-	~~Several made in [http://www~~.~~eros-os.org/pipermail/e-lang/2009-January/012968.html]. [If opinions are expressed, expand this section to mention them specifically.]~~	+	None yet.

	==Discussion==		==Discussion==

-	* [http://www.eros-os.org/pipermail/e-lang/2008-March/012520.html Initial report~~] by [[User:Kevin Reid]~~].	+	* [http://www.eros-os.org/pipermail/e-lang/2008-March/012520.html Initial report].
-	* [http://www.eros-os.org/pipermail/e-lang/2009-January/012968.html Second report] by Kevin Reid (who forgot he had written the first)	+

	[[Category:Unresolved design issues]]		[[Category:Unresolved design issues]]