From: Andre P. <at...@us...> - 2004-05-17 18:06:48
|
Update of /cvsroot/hoc/hoc/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv22025 Modified Files: Makefile.in Mapping_Types.pod Added Files: README.txt Log Message: Added docs/README.txt Index: Makefile.in =================================================================== RCS file: /cvsroot/hoc/hoc/docs/Makefile.in,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- Makefile.in 14 May 2004 06:05:15 -0000 1.2 +++ Makefile.in 17 May 2004 18:06:38 -0000 1.3 @@ -1,6 +1,13 @@ +include ../config.mk + +dist_srcdir = docs +dist_FILES = \ + $(SOURCE_PODS) \ + Makefile.in \ + $(NULL) + TITLE = HOC: a Haskell to Objective-C bridge -NULL = SOURCE_PODS = Introduction.pod \ Quick_Start.pod \ Mapping_Types.pod \ Index: Mapping_Types.pod =================================================================== RCS file: /cvsroot/hoc/hoc/docs/Mapping_Types.pod,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- Mapping_Types.pod 10 May 2004 18:07:23 -0000 1.3 +++ Mapping_Types.pod 17 May 2004 18:06:38 -0000 1.4 @@ -9,6 +9,19 @@ =head3 Protocols +=begin comment + +Yes, formal protocols. Luckily, they're very rarely used in +Cocoa. It's only an ifgen issue; the current ifgen just +generates ID for all id<Foo> types. For id<Foo,Bar> used as +a parameter, it should generate (Foo (ID a), Bar (ID a)) => ID a. +For return values id<Foo,Bar>, we'll have to define a special +type ID_Bar_Foo and declare instances for Foo and Bar for it. The +only difficult part should be to avoid defining those types too +often... + +=end comment + =head3 Protocol Adoptions =head2 Object Messaging --- NEW FILE: README.txt --- The documentation files in this directory are Perl POD (Plain Old Documentation) markup files. If you're not familiar with POD markup, type ``man perlpod'' in a Terminal for more information, or see: <http://www.sunsite.ualberta.ca/Documentation/Misc/perl-5.6.1/pod/perlpod.html>. |