From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eddward DeVilla" Subject: Re: Re: Release 6.17 Date: Sun, 4 Jan 2009 14:58:34 -0600 Message-ID: References: <1AD01E3D-3A98-4811-A7A1-0491189CE5C0@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LJa3T-0002x9-4X for emacs-orgmode@gnu.org; Sun, 04 Jan 2009 15:58:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LJa3S-0002wp-Aj for emacs-orgmode@gnu.org; Sun, 04 Jan 2009 15:58:38 -0500 Received: from [199.232.76.173] (port=36692 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LJa3S-0002wm-83 for emacs-orgmode@gnu.org; Sun, 04 Jan 2009 15:58:38 -0500 Received: from wa-out-1112.google.com ([209.85.146.179]:11499) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LJa3R-0002kq-LZ for emacs-orgmode@gnu.org; Sun, 04 Jan 2009 15:58:37 -0500 Received: by wa-out-1112.google.com with SMTP id j32so4077824waf.26 for ; Sun, 04 Jan 2009 12:58:34 -0800 (PST) In-Reply-To: <1AD01E3D-3A98-4811-A7A1-0491189CE5C0@uva.nl> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org, "Steven E. Harris" On Sun, Jan 4, 2009 at 10:01 AM, Carsten Dominik wrote: > > On Jan 4, 2009, at 3:33 PM, Steven E. Harris wrote: > >> Carsten Dominik writes: >> >>> Code references use special labels embedded directly into the source >>> code. Such labels look like "((name))" and must be unique within a >>> document. >> >> How does the parser know that, say, "((def))" is not a valid expression >> in the surrounding Lisp forms? Is it important that it be separated by >> space, or be the last token on the line? >> >> Trying to concoct a motivating example, consider a structure represented >> as nested lists: >> >> ,---- >> | '(a >> | ((b c) d) >> | (((e) f)) ((def)) >> | g) >> `---- >> >> Without knowing what the enclosing `quote' form means, how do know that >> "((def))" is not part of it? > > Hi Steven, > > good question, and the answer is that is does not know, > cannot know, because this is a feature that is supposed > to work for any kind of example, an the parser cannot > know all possible syntaxes :-) > > This idea is to make this work in a heuristic way, by using something > that is unlikely enough to occur in real code. > > You are right that what I am using might be too > dangerous for emacs lisp or other lisp dialects, and > it could also show up in other languages like C. > > What would be safer? > > <> like the other Org-mode targets? That would make sense. > Does anyone know a language where this would be used > in real life? It would make it harder to write about > Org-mode, though. > > Or do we need another option, so that, if needed, we could switch do > a different syntax? > > Comments are very welcome. > > - Carsten I think that is quote words in perl 6. @list = <<$this is a 'list' of 7 strings>> # in perl 6 is @list = qw/$this is a 'list' of 7 strings/ # in perl 5. It's looking like perl 6 will be a reality and that syntax is recommend in several places like hash dereferences. %hash<> # look up bareword in %hash I can't remember enough off the top of my head, but I think <> will play merry heck with common(?) perl 6 code. I can look up more examples if needed. Edd