unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: freeing srcprops ?
Date: Fri, 19 Jan 2007 10:28:28 +1100	[thread overview]
Message-ID: <87fya7ap9f.fsf@zip.com.au> (raw)
In-Reply-To: <45AF7E7F.1000600@xs4all.nl> (Han-Wen Nienhuys's message of "Thu,  18 Jan 2007 15:04:47 +0100")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>  SCM
>  scm_make_srcprops (long line, int col, SCM filename, SCM copy, SCM plist)
>  {
> +  if (!SCM_UNBNDP (filename))
> +    plist = scm_acons (scm_sym_filename, filename, plist);

Can those two cells be shared among all source props for the same
file, to save space?

> +  SCM_RETURN_NEWSMOB3 (scm_tc16_srcprops,
> +		       SRCPROPMAKPOS (line, col),

If col is a freaky big value then perhaps put it in the plist.  Could
be helpful if there's stupidly long lines in some generated code file,
wouldn't cost anything normally.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2007-01-18 23:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  0:22 freeing srcprops ? Han-Wen Nienhuys
2007-01-18 14:04 ` Han-Wen Nienhuys
2007-01-18 23:28   ` Kevin Ryde [this message]
2007-01-19 10:37     ` Han-Wen Nienhuys
2007-01-19 11:52     ` Han-Wen Nienhuys
2007-01-26 22:15       ` Kevin Ryde
2007-01-26 23:33         ` Han-Wen Nienhuys
2007-01-18 23:20 ` Kevin Ryde
2007-01-28  9:08   ` Neil Jerram
2007-01-29 11:39     ` Han-Wen Nienhuys
2007-01-29 21:35       ` Neil Jerram
2007-01-29 23:31         ` Han-Wen Nienhuys
2007-01-30 12:40           ` Ludovic Courtès
2007-01-30 19:14             ` Han-Wen Nienhuys
2007-01-30 12:21       ` Mikael Djurfeldt
2007-01-30 12:52         ` Han-Wen Nienhuys

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87fya7ap9f.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-devel@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).