9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] source code as data not text
Date: Mon, 18 Jun 2001 22:31:03 +0100	[thread overview]
Message-ID: <200106182131.WAA02827@localhost.localdomain> (raw)
In-Reply-To: Message from David Gordon Hogan <dhog@plan9.bell-labs.com>  of "Mon, 18 Jun 2001 14:48:35 EDT." <20010618184843.68F9819A00@mail.cse.psu.edu>

dhog:
> What if the code were accessed through a file system interface
> which is cross-platform?

As has been pointed out, how something is stored isn't that relevant
here; the issue is *what*, and the principle issue is whether your
program is stored as ascii source, or as some other representation
(that presumably adds additional structuring, else why bother?)

If you're storing an ascii file, then whether you store it in
a cvs-like system, an RDBMS or something entirely different isn't
that much more important than whether it's stored in a file system
that's on a local disk or a networked one: you may need to use
special means to retrieve it, but that's your call.

If it's plain ascii, and you've got an editor that can show pretty
colours, then fine. I'm happy for you, and it doesn't mean that anything
special has to be done to the file that'll stop it working on any other
editor.

If your source file is saved as something that represents additional
structure, then I'd suggest you're using the wrong terminology: that's
an object file, that's been compiled into another representation. From
here on in, you need a special set of tools to interpret and manipulate
the contents of that file. Regardless of the means by which you retrieved
the file, it's effectively a black box to most of the surrounding
system.

As I've said for many a year, "standardise on file formats and protocols,
and the applications take care of themselves."

steve




  reply	other threads:[~2001-06-18 21:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dhog@plan9.bell-labs.com>
2001-06-18 18:48 ` David Gordon Hogan
2001-06-18 21:31   ` Steve Kilbane [this message]
2001-06-19 21:03     ` Richard Elberger
2001-06-19 21:31       ` Steve Kilbane
2001-06-19  7:36   ` Richard Elberger
2001-06-28 22:17   ` Boyd Roberts
2001-07-11 17:53 ` [9fans] sam vs acme David Gordon Hogan
2001-07-11 19:19   ` James A. Robinson
2001-07-11 21:15     ` Steve Kilbane
2001-07-11 23:11   ` Boyd Roberts
2001-11-01 21:19 ` [9fans] Virtual memory in BSD and Plan9 David Gordon Hogan
2001-11-01 21:23   ` Scott Schwartz
2001-11-21  0:12 ` [9fans] on TCP vs IL David Gordon Hogan
2001-11-21  0:21   ` George Michaelson
2001-11-22  9:57   ` Thomas Bushnell, BSG
2001-11-23  9:34     ` Douglas A. Gwyn
2001-11-26 10:00       ` Thomas Bushnell, BSG
2001-11-26 15:21         ` Douglas A. Gwyn
2001-12-07 19:41 ` [9fans] libXg/test.c David Gordon Hogan
2001-12-07 20:08   ` Boyd Roberts
2001-12-07 20:09   ` Scott Schwartz
2001-12-07 20:28     ` Boyd Roberts
2001-12-10 10:01     ` Maarit Maliniemi
2001-12-11 16:51   ` Leo Caves
2002-09-17 22:04 ` [9fans] /sys/src/^(9 boot)^/pc/memory.c David Gordon Hogan
2002-09-17 22:08   ` Scott Schwartz
2001-06-28 21:17 [9fans] source code as data not text Boyd Roberts
  -- strict thread matches above, loose matches on Subject: below --
2001-06-18 15:24 anothy
2001-06-19  3:52 ` Richard Elberger
2001-06-18 14:45 anothy
2001-06-19 16:51 ` Barry
2001-06-18  7:45 nigel
2001-06-18  7:43 nigel
2001-06-18  9:07 ` Laura Creighton
2001-06-28 21:00   ` Boyd Roberts
2001-06-28 22:02   ` Boyd Roberts
2001-06-18  0:31 Matt
2001-06-18  8:52 ` Laura Creighton
2001-06-18  9:13   ` Matt
2001-06-18 10:02     ` Richard Elberger
2001-06-18 14:56   ` Dan Cross
2001-06-28 21:56 ` Boyd Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200106182131.WAA02827@localhost.localdomain \
    --to=steve@whitecrow.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).