Chad J wrote:
> For the rest of us, would you consider having a wrapper for that stuff included in Tango?

Can't promise anything, but I'll certainly run it by folks here


>> Not yet. Want to write one?
>>
> 
> Sure.
> 
> Problem is though, I'm in a bit of time crunch with midterms, scholarship essays, and my father's birthday, so I probably wouldn't be able to even start for another week or so.  Is that OK?

Absolutely :)


> OK, thanks.  Yeah, that's a bit inconvenient.  Hope dmd changes then.

That would be great if it did. If a change were to happen there, it might be worth pursuing something about -g switching to a different lib, or a different sc.ini libspec? maybe.


>> That's a good point. And at this time we don't have a quick reference per se [writes a ticket for it].
>>
>> FWIW, untyped data in Tango is invariably returned as a void[], and the API links are pretty good even if the doc isn't always complete -- the doc API uses CandyDoc, and the big-blue-title at the top leads to a Decant generated source listing. All the other blue links on the CandyDoc pages lead to Wiki comments, which we'll uses for improving the code doc etc. Quite sophiticated really, for API doc :)
>>
> 
> Might I suggest that ubyte[] or byte[] be a more appropriate return type for some of those arrays due to the type-awareness of the GC?  It would suck to read in a "noisy" data file and have the GC choke on it, or have to always tell the GC that there are no pointers there.  I'm assuming you will never find valid pointers to memory in a file from a drive, or if you do, the GC probably wasn't scanning the file anyways so you'd have problems if you didn't already have a safety reference.

Yes. There just wasn't enough time to doink all of those since the compiler release. Under the covers, though, methods like File.read() allocate a byte[], but return it as a void[] to indicate the lack of known type. If I understand correctly, this should address your concern?

Lars Ivar Igesund wrote:
> Dear D community
> 
> The first public release of Tango is now ready for download.
> 
Thanks.

Zz

Chad J wrote:
> When I try to use it though, I get the following compiler error:
> 
> --------------------------
> 
> C:\Dprojects\tango>build main.d -clean
> Assertion failure: 'classinfo->structsize == CLASSINFO_SIZE' on line 315 in file
>   'toobj.c'

Revision 1378 of Tango works with dmd 1.0.  It's tagged for dmd 1.000. I haven't tried later revisions.  DWT doesn't work with dmd 1.004, so I'm holding off on upgrading.  I expect other people are in the same situation.  This will probably change, since the cause seems to be a bug in dmd 1.004, related to missing or wrong TypeInfo instances.


 > Is there any way I could make my programs that still use phobos compile
> again without uninstalling Tango?
> 

I have sc.ini.phobos and sc.ini.tango, and just replace sc.ini with the relevant one when I want to switch libs.  If you follow the installation instructions on the web site, switching between phobos and tango is really that easy.  sc.ini.phobos is the default one, sc.ini.tango is edited following the installation instructions on this page:

http://www.dsource.org/projects/tango/wiki/WindowsInstall

A minor nit:

On page http://www.dsource.org/projects/tango/wiki/ChapterMath,
the text does not wrap on Explorer, making for very long lines.

On Fri, 02 Feb 2007 11:28:12 -0800, Walter Bright wrote:

> A minor nit:
> 
> On page http://www.dsource.org/projects/tango/wiki/ChapterMath, the text does not wrap on Explorer, making for very long lines.

Confirmed for IE 7

BTW, it looks fine using Firefox 1.5.0.9 and Opera 9.10.

-- 
Derek Parnell

Walter Bright wrote:
> A minor nit:
> 
> On page http://www.dsource.org/projects/tango/wiki/ChapterMath,
> the text does not wrap on Explorer, making for very long lines.

Thanks for finding that.  I think we'll have that patched up soon. ;)

http://www.dsource.org/projects/tango/ticket/253

-- 
- EricAnderton at yahoo

Pragma wrote:
> Walter Bright wrote:
>> A minor nit:
>>
>> On page http://www.dsource.org/projects/tango/wiki/ChapterMath, the text does not wrap on Explorer, making for very long lines.
> 
> Thanks for finding that.  I think we'll have that patched up soon. ;)
> 
> http://www.dsource.org/projects/tango/ticket/253
> 

all set

BA

Lars Ivar Igesund wrote:
> The first public release of Tango is now ready for download.

This is a first rate example of what the D community can do. Congratulations to everyone involved in its creation. You guys have set the bar pretty high!

Chad J wrote:
> Is there any way I could make my programs that still use phobos compile again without uninstalling Tango?

I have my home directory set up to make this easy.  When I get a new D compiler, I unzip it under ~/d/d.1.004 (or wherever).  Then I create this symbolic link:

/home/me/d/current -> /home/me/d/d.1.004

Make the binaries executable, fix dmd.conf, and its ready to go.

The following links never change, they redirect everything through "current":

/etc/dmd.conf -> /home/me/d/current/dmd/bin/dmd.conf
/usr/lib/libphobos.a -> /home/me/d/current/dmd/lib/libphobos.a
/home/me/bin/dmd -> /home/me/d/current/dmd/bin/dmd
/home/me/bin/rdmd -> /home/me/d/current/dmd/bin/rdmd
/home/me/bin/obj2asm -> /home/me/d/current/dmd/bin/obj2asm
/home/me/bin/dumpobj -> /home/me/d/current/dmd/bin/dumpobj

I can change the "current" symlink to get a particular version of D.

I imagine in Windows you could use rename instead of symbolic links to achieve almost the same effect.  With a little more tweaking I could switch D versions with an evironment variable.

Kevin

Walter Bright wrote:
> Lars Ivar Igesund wrote:
> 
>> The first public release of Tango is now ready for download.
> 
> This is a first rate example of what the D community can do. Congratulations to everyone involved in its creation. You guys have set the bar pretty high!

No and/or here, it's _both_!

Walter and the Tango guys:

Cool, both! Congrats!!!!



Wish I'd been there, but lately I've been (luckily only) almost electrocuted to death just 3 (three) times simply the last week!

(One of them: 500V DC, 125A. I happened to poke the wrong thing in the connection box with my multimeter. Result: a bang that locked my ears, a spark that scared the audience, a jolt that threw me back two steps without "moving a limb", and a darkness that impressed the guys at the other shops in the block.) There's a rumor we're doing something "heavy". Not likely we'll clip that one anymore. Oh, and my multimeter minus side probe is 1/4" shorter now.

We're in Europe, so the green-yellow striped one is the shield ground wire. My associate fastens all three wires while he's talking gossip and the weather and NOT looking at what he's doing. He's like the film star in the car scene, driving and explaining the plot to the female co-star: never even glimpsing the road.

There were 18 plugs he had to wire, and (only after some near-misses of life) it turned out he'd miswired more than half of them. Honestly, I'd want to "teach" him with a shotgun. :-( !!!!! I've got three minor kids, for chrissake!

I'm now doing software for our second Extruder Unit, which is very different from the first one. For one thing, the watch points went from 6 to 10, and then we got 5 pressure points to monitor too. And it's been shown to me that a thermostat-like temperature control simply is not adequate anymore. We need some kind of adaptive or pre-emptive, or learning, temperature "intelligence" with this new machine. (Anybody have any pointers, hints or ideas?) And looks like it'd have to "learn" from the motor rpm+amperes+voltage + temperatures+pressures + first-and-second-derivatives-of-them, and Bob knows what -- to become prescient, or at the very least, "aware".

(My associate would not exactly understand if any of you guys would suggest I'd tell him he's demanding more than Cyberdyne Systems contributed to Skynet.)