IRC channel logs

<bjc>RhodiumToad: thanks, i was kind of figuring it wasn't possible, but hope springs eternal

<RhodiumToad>in particular, if module A imports B which imports something from C and re-exports it, I don't think you can find out that it came via B

<RhodiumToad>you might be able to tell that the variable exists in both B and C, but that's it

<old>in theory,procedure-source would be it no?

<old>however it returns #f for everything

<RhodiumToad>procedure-source is the source code, not the origin module

<RhodiumToad>but yes, it's not usually available

<old>ahh okay

<mwette>With match-lambda, is it possible to create a rule to return the argument if it is a string? (match-lambda ((? string?) ???))

<mirai>mwette: ((? string? x) x)) ?

<mwette>ah, yes; thanks mirai

<mwette>how do I add namespace to sxml? SXML.scm says (*TOP* (@ (*NAMESPACES* (xhtml "path/to/xhtml"))) ...)

<mwette>but sxml->xml doesn't accept that

<RhodiumToad>did ssax ever get fixed in guile?

<RhodiumToad>sec, I did some stuff with namespaces in sxml, let me look it up

<RhodiumToad>dammit, the ssax bug is still there in guile

<mwette>I got something to work by adding an attribute to the top-level object: (*TOP* (form (@ (xmlns:h "path/to/spec")) ...))

<RhodiumToad>so looking at the code, the (sxml simple) functions basically have negligible namespace support

<RhodiumToad>xml->sxml has the ability to map namespaces to prefixes, but that's all

<RhodiumToad>ssax itself can do more, but isn't as easy to use

<RhodiumToad>(the ssax bug is with the handling of reading CDATA elements, it was fixed upstream years ago)

<mwette>RhodiumToad: thanks a bunch ; I remember the CDATA discussion

2023-04-15.log