summaryrefslogtreecommitdiff
path: root/open_issues/elinks.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-07-24 12:23:41 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-07-24 12:23:41 +0200
commit2fd0d6136e613c86a8ca1494475b6d21f4ba97da (patch)
tree794fa5a7a6d612da39d4be1401fbbc1a2a2cdf32 /open_issues/elinks.mdwn
parent95f6c960295ee7229c7e7f54575918b46a7310af (diff)
open_issues/elinks: New.
Diffstat (limited to 'open_issues/elinks.mdwn')
-rw-r--r--open_issues/elinks.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/open_issues/elinks.mdwn b/open_issues/elinks.mdwn
new file mode 100644
index 00000000..ff1bd46a
--- /dev/null
+++ b/open_issues/elinks.mdwn
@@ -0,0 +1,24 @@
+[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_porting]]
+
+IRC, unknown channel, unknown date
+
+ <paakku> In elinks/src/network/state.h, there is an assumption that values of errno are between 0 and 100000. Now looking at glibc-2.5/sysdeps/mach/hurd/bits/errno.h, I see that you're using values outside this range. Have there been problems because of this?
+ <youpi> eeerf
+ <youpi> I had never seen a program assuming that
+ <youpi> that sucks
+ <paakku> It can be fixed, but that'd require some work, so I'd like to first have a clear idea of the effects.
+ <youpi> fixed where ?
+ <paakku> in elinks
+ <youpi> k
+ <paakku> by allocating just one number from our enum connection_state for system errors, and then stashing the errno value in a separate variable.
+ <paakku> Anyway, if you see this cause any user-visible bugs in ELinks, please report.