[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] Re: [Chicken-bugs] #382: port-name problem
From: |
Chicken Scheme |
Subject: |
[Chicken-janitors] Re: [Chicken-bugs] #382: port-name problem |
Date: |
Mon, 03 Dec 2007 12:46:40 -0000 |
#382: port-name problem
-----------------------+----------------------------------------------------
Reporter: elf | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: compiler | Version: 2.7
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Comment (by felix):
Replying to [ticket:382 elf]:
> port-name's return value is ambiguous, as the tagged parenthesised
symbols are valid filenames as well. suggestion to remedy this: file
ports return string values corresponding to the filename. all others
return the tag as a symbol, rather than a string. i also suggest putting
explicit quotation marks around the filename for the display
representation.
You are right, of course, but I wouldn't want to change the current
semantics, as this will break backwards compatibility. I implement the
latter suggestion.
--
Ticket URL: <http://trac.callcc.org/ticket/382#comment:1>
Chicken Scheme <http://www.call-with-current-continuation.org/>
The CHICKEN Scheme-to-C compiler
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-janitors] Re: [Chicken-bugs] #382: port-name problem,
Chicken Scheme <=